Opinion
What you think. Why you built it, what everyone else gets wrong, and where this goes next. Developers choose the product with a point of view.
Writing for developers. And 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
“Can't recommend Argot enough. They have deep technical knowledge—you get authentic, developer-to-developer material that adds value. They can write thought-leadership just as well as technical content, which is very hard to find. Responsive and never miss a deadline.”
Thought for developers
Developers are working at a higher level of abstraction. They need the why and the what more than the how.
How we workExplainers
What you know. Intuition from your years on the problem, set out so developers learn from the subject matter experts.
Tutorials
What you do. A real build, start to finish, so developers see what’s possible before they decide what to build.
How-to guides
How it works. One problem and how your product fixes it. Enough to trust it with their problems.
Run by agents
Agents are doing the how now. They need it exact, short, and working the first time.
how-tos.md
How it works. An agent hits one problem mid-task and needs it fixed now. The exact fix, runnable as written.
tutorials.md
What you do. An agent using your product for the first time has only your tutorial to go on. Every step runs in order.
explainers.md
What you know. An agent choosing an approach needs the concept in its context.
opinion.md
What you think. When a developer asks their agent what to use, it answers with what it has read.
Blank page, rough draft, or no plan yet
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 find where your docs stop and the integration breaks.
Developers and their agents both work from what you've published. We find the gaps, decide what to write to close them, and add the comparison pages and explainers that get your product 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
Mostly about writing. Increasingly about agents.
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 writeQuestions
Short answers about what we write and how we work.
Argot is a technical content marketing agency for developer tools and AI products. It writes, edits and plans tutorials, how-to guides, explainers and opinion for developers and the agents they use.
What should developers build with your product?
Send us a few lines about the product, who uses it, and what you want them to build. We'll come back with ideas for what to write.