Tutorials
Step-by-step guides that walk developers through building real things with your product.
Writing for developers. Clear enough for their agents.
Tutorials, guides, explainers, and opinion, written for the humans and machines that ship code.
agent-pay.jsclick a line
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";import { ExactEvmScheme } from "@x402/evm/exact/client";import { privateKeyToAccount } from "viem/accounts"; const agent = privateKeyToAccount(process.env.AGENT_KEY);const payees = new Set([process.env.QUOTES_WALLET.toLowerCase()]); const client = new x402Client() .register("eip155:8453", new ExactEvmScheme(agent)) .setSpendControls({ maxAmountPerPayment: "$0.05" }) .onBeforePaymentCreation(async ({ selectedRequirements }) => { const payTo = selectedRequirements.payTo.toLowerCase(); if (!payees.has(payTo)) return { abort: true, reason: `Unknown payee ${payTo}` }; }); const payFetch = wrapFetchWithPayment(fetch, client);const res = await payFetch("https://api.example.com/v1/quotes");01 / 05
Give the agent its own wallet
Every payment gets signed with this key, so don’t give the agent a wallet with anything else in it. Set up a new one and fund it with only what you’re happy for the agent to spend. It doesn’t need any ETH either. What the agent signs is an authorization to move USDC, and a facilitator submits that on chain and covers the gas.
Written for teams at
Deno
Modal
Stream
Content developers actually want to read
Clear, accurate writing that shows what your product can do. Every snippet runs and every command executes.
How we workHow-to guides
Focused articles that solve specific problems your users face.
Explainers
Deep dives into technical concepts that show where your product fits.
Opinion
Essays under your founder's name that take a position developers can argue with.
Skip the vetting, briefing, and rewriting
Hiring writers one by one means testing them, explaining your product, and fixing drafts that miss the technical details.
We learn your product and test every example ourselves, so the first draft already holds up to technical scrutiny.
Three ways to work with us
We write from scratch, fix what you already have, or work out what to publish next.
Writing
We build with your product before we write a word.
Every line of code in a draft has run before you see it. We write tutorials, guides, explainers, comparison pages, and essays under your founder's name.
Editing
We cut the slop from your drafts.
Send us what your team or your model wrote. We run the code, cut anything wrong or generic, and send it back ready to publish. Old tutorials too, since coding agents now follow them step by step.
Strategy
We plan for developers and their agents.
Both work from what you've published. We find where that breaks down on the way to a working integration and what to write to fix it, plus the comparison pages and explainers that help your product get picked in the first place.
Written to be read, then run
Four rules every piece follows, from the first outline to the final edit.
Why before how
// Agents can handle the how. Your content has to answer why.
Written for two readers
// Machines read your docs and act on them. If they can't follow it, it isn't ready.
If it's written, it runs
// Every snippet and command on the page works in a terminal.
Models draft, people finish
// LLMs are great for getting ideas down, not out. Taste is still human.
Notes on technical writing
Notes on technical writing, developer marketing, and the machines now reading both.
Developers who can write, we pay you to
Who pays technical writers? We do. Send a few links to technical writing you are proud of, with bonus points if you built the thing you wrote about.
Apply to writeTell us about your product
Send us a few lines about your product, your audience, and what you want developers to build.