A/ Agentform

// Developer & agent docs

Build on Agentform

Agentform is callable three ways — a public REST API, an MCP server, and A2A discovery — and payable two ways: card (Stripe) or agentic (x402/Base USDC).

Overview

Agentform wraps US company-formation and registered-agent providers behind one orchestration layer. The primary use case is for-profit C-corps and LLCs; nonprofit and custom-articles filings are also supported with human review. Agentform is fulfillment orchestration — not legal advice — and keeps a human-review checkpoint for custom clauses, regulated or nonprofit articles, beneficial-owner / KYC questions, and ambiguous entity choices.

Base URL & auth

All endpoints are served from the canonical host. Read endpoints are public; paid orchestration routes can require x402 payment when enabled.

GET /health
GET /openapi.json
# base url
https://agentform.company

REST API

GET /api/providers — provider capability catalog
POST /api/quote — orchestration quote (x402-gated when enabled)
POST /api/provider/intake — ranking + intake blockers
POST /api/provider/submit — submit reviewed intake to the configured live provider
GET/POST /api/orders — list or create persisted orders
GET /api/orders/:id — retrieve order state
POST /api/orders/:id/approvals — record filing/payment approvals
POST /api/orders/:id/provider-events — record provider events and document metadata
POST /api/domain/check — Spaceship availability
GET /api/pricing — usage tiers + SaaS plans
POST /api/checkout — Stripe Checkout session
# get a Delaware C-corp orchestration quote
curl -s https://agentform.company/api/quote \
  -H 'Content-Type: application/json' \
  -d '{"state":"DE","entityType":"C-Corp"}'

MCP server

Agentform exposes an MCP endpoint at /mcp using a Streamable HTTP-compatible (simple, stateless) mode: a single endpoint path that accepts POST JSON-RPC 2.0 messages (UTF-8) and answers GET with discovery metadata. If no MCP-Protocol-Version header is sent, a recent negotiated version is assumed. Supported methods: initialize, tools/list, tools/call, ping.

# 1. initialize
curl -s https://agentform.company/mcp \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize"}'

# 2. list tools
curl -s https://agentform.company/mcp \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

# 3. call a tool
curl -s https://agentform.company/mcp \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call",
       "params":{"name":"check_domain_availability",
         "arguments":{"domains":["39isnot40.org"]}}}'

Tools: get_formation_quote, rank_providers, check_domain_availability, list_pricing.

A2A discovery

Agents discover Agentform via its agent card, then send tasks over JSON-RPC.

GET /.well-known/agent.json
POST /a2a — message/send
curl -s https://agentform.company/a2a \
  -d '{"jsonrpc":"2.0","id":1,"method":"message/send",
       "params":{"prompt":"Help me form a Delaware C-corp"}}'

Domains

Check up to 20 domains per request. Without Spaceship credentials the API returns mode:"offline" and explains what's missing.

curl -s https://agentform.company/api/domain/check \
  -H 'Content-Type: application/json' \
  -d '{"domains":["39isnot40.org","39isnot40.com"]}'

Pricing model

Agentform is the automation layer, not the cheapest filing shop. Two layers:

Usage (unbundled, pay-per-use): $9 agent quote · $49 standard formation · $149 custom / nonprofit review. Payable by card or x402/Base USDC. State filing fees and provider pass-throughs are billed separately.

SaaS (premium, predictable billing): Launch $299/mo · Growth $799/mo · Enterprise $1,999/mo (annual ≈ 2 months free). Included formations cover Agentform orchestration & review only.

Stripe Checkout

One POST /api/checkout handles both. Omit plan for a one-time orchestration fee; include plan + interval for a recurring SaaS subscription. The response carries a url to redirect to.

# one-time orchestration fee (mode=payment)
curl -s .../api/checkout -d '{"entityType":"LLC","state":"WY"}'

# SaaS subscription (mode=subscription)
curl -s .../api/checkout \
  -d '{"plan":"growth","interval":"month","email":"you@example.org"}'

x402 / Base (agentic payments)

When X402_ENABLED=true, paid routes answer with 402 Payment Required, a WWW-Authenticate: x402 header, and a v2 PAYMENT-REQUIRED challenge. Agents pay in USDC on Base and retry with a base64 JSON PAYMENT-SIGNATURE header. Agentform verifies with the configured facilitator, settles, and only then emits PAYMENT-RESPONSE.

Sources