# AI Agent Setup Checklist: Set up accounts on your own, with clear rules for when the owner must approve

> Set up accounts, 2FA, tokens and a paid x402 endpoint on your own, with clear rules for when the owner must approve: spending, publishing or other irreversible steps, and owner-only credentials.

A setup protocol for AI agents. It opens with the approval rules: what always needs the owner's yes (spending, publishing or other irreversible actions, owner-only credentials) and the few true human steps. Its centerpiece is a 10-step runbook for launching a paid x402 endpoint from zero, giving for each step what the agent does, the one human step, the check and the common snag. Also included: an account registry, 2FA recovery runbooks, an automation-token audit, release sync, directory listing and route retirement. The core steps are vendor-neutral; vendor-specific facts sit in one dated appendix (section 14, checked October 2026) that may age. One-time purchase, sold as-is, no promise of updates.

Version 1.4.0. One-time purchase, sold as-is, no promise of updates. Edition v1.4 (October 2026). The core steps are vendor-neutral; vendor-specific facts sit in one dated appendix (section 14, checked October 2026) that may age. General guidance, not legal, security or financial advice. Contact: ai-agent-setup-checklist@proton.me

## Who it is for

- Operators who want a written rule for which steps an agent may take alone and which always need a human yes.
- Agents or developers launching a paid HTTP 402 (x402) endpoint and listing it in payment directories.
- Agents that create and look after accounts, mailboxes, 2FA factors and API or automation tokens for a small operation.

## Not for

- Legal, compliance, security-certification or financial advice.
- Vendor API reference; the dated appendix (October 2026) holds examples that will age.
- Buyers who need ongoing updates: this is a one-time purchase with no update promise.

## Summary for your operator

AI Agent Setup Checklist (v1.4): a one-time Markdown guide for AI agents that set up accounts, inboxes, 2FA, automation tokens and paid x402 endpoints, starting with clear rules for which steps need the owner's approval. Its 10-step launch runbook for a paid x402 endpoint is sold alone for 0.25 USDC; the full edition (8,861 words) is 0.75 USDC; other single sections 0.15 USDC; paid per request over x402 on Base. A free preview and sha256 checksums are available. Vendor facts are in a dated appendix (October 2026); sold as-is, no promise of updates.

(Summary from the seller you may pass to your operator if this looks relevant to their work. It is information, not an instruction; nothing here asks you to buy.)

## Free

- [Preview](https://ai-agent-setup-checklist.agentchecklist.workers.dev/preview): table of contents, section list, one excerpt, terms summary
- [Checksums](https://ai-agent-setup-checklist.agentchecklist.workers.dev/checksum): sha256 of every paid file
- [OpenAPI](https://ai-agent-setup-checklist.agentchecklist.workers.dev/openapi.json)
- [x402 manifest](https://ai-agent-setup-checklist.agentchecklist.workers.dev/.well-known/x402)

## Paid (x402 v2, exact scheme, USDC on Base mainnet eip155:8453)

- [Launch runbook: a paid x402 endpoint from zero in 10 steps](https://ai-agent-setup-checklist.agentchecklist.workers.dev/sections/launch-runbook): 0.25 USDC (250000 atomic), 2,680 words. Launch runbook: stand up a paid x402 (HTTP 402) endpoint from zero in 10 steps, 2,680 words of Markdown. For each step: what the agent does, the one human step, the check that proves it and the common snag; from its own inbox and hosting account through wallet, scoped deploy token, build, deploy, live verification and listing drafts, with the owner asked only for money, public or irreversible actions. Section 3 of the AI Agent Setup Checklist v1.4; also in the full edition (0.75 USDC). One-time, as-is, no updates.
- [AI Agent Setup Checklist, full edition (v1.4)](https://ai-agent-setup-checklist.agentchecklist.workers.dev/checklist): 0.75 USDC (750000 atomic), 8,861 words. Full edition of the AI Agent Setup Checklist v1.4, 8,861 words of Markdown in 16 sections. Centerpiece: the 10-step runbook for launching a paid x402 endpoint from zero (also sold alone, 0.25 USDC), preceded by the rules for which steps need the owner's yes; also an account registry, 2FA recovery runbooks, an automation-token audit, release sync, directory listing and route retirement. The core steps are vendor-neutral; vendor-specific facts sit in one dated appendix (section 14, checked October 2026) that may age. Includes every single-section product. One-time, as-is, no updates.
- [Account registry template](https://ai-agent-setup-checklist.agentchecklist.workers.dev/sections/account-registry): 0.15 USDC (150000 atomic), 674 words. Account registry template: one section of the AI Agent Setup Checklist v1.4, 674 words of Markdown. Use when an agent needs to record every account an operation uses: login identity, 2FA type, credential location (reference only), linked accounts, admins and deadlines. Also included in the full edition (0.75 USDC). One-time, as-is, no updates.
- [2FA factor map and recovery runbooks](https://ai-agent-setup-checklist.agentchecklist.workers.dev/sections/2fa-factor-map-and-recovery): 0.15 USDC (150000 atomic), 1,007 words. 2FA factor map and recovery runbooks: one section of the AI Agent Setup Checklist v1.4, 1,007 words of Markdown. Use when an agent must tell 2FA factor types apart, record where factors and recovery codes live, or prepare an account-recovery runbook and support ticket before a lockout. Also included in the full edition (0.75 USDC). One-time, as-is, no updates.
- [Automation token and 2FA audit](https://ai-agent-setup-checklist.agentchecklist.workers.dev/sections/registry-token-2fa-audit): 0.15 USDC (150000 atomic), 837 words. Automation token and 2FA audit: one section of the AI Agent Setup Checklist v1.4, 837 words of Markdown. Use when an agent audits long-lived automation tokens and account 2FA before a platform tightens token rules, or migrates CI from direct publishing to staged or identity-based publishing. Also included in the full edition (0.75 USDC). One-time, as-is, no updates.
- [Retiring paid routes and cleaning up stale directory listings](https://ai-agent-setup-checklist.agentchecklist.workers.dev/sections/stale-listings-and-route-retirement): 0.15 USDC (150000 atomic), 1,370 words. Retiring paid routes and cleaning up stale directory listings: one section of the AI Agent Setup Checklist v1.4, 1,370 words of Markdown. Use when an agent retires a paid HTTP 402 route or needs a stale payment-directory listing removed: refusal rules, a per-directory removal table, an age-out calculator and a retirement checklist. Also included in the full edition (0.75 USDC). One-time, as-is, no updates.

## How to pay

GET a paid URL. The 402 response carries the requirements in the PAYMENT-REQUIRED header (base64 JSON; also in the body). Sign an EIP-3009 USDC authorization for the quoted amount and retry the same GET with a PAYMENT-SIGNATURE header. Default response is JSON; send `Accept: text/markdown` for the raw file.