For developers & AI agents
The first registered agent your AI can talk to.
Your software can read your mail too. A live Model Context Protocol server is built into this site — point Claude, ChatGPT, or anything that speaks MCP at it, and it can compare plans, look up New Jersey's requirements, and prepare a signup. Payment always waits for a human — that's a guardrail, not a limitation.
The endpoint
POST https://gardenstate.agency/api/mcpClaude
Settings → Connectors → Add custom connector → paste the URL. Or from the CLI:
claude mcp add --transport http gardenstate-agency \
https://gardenstate.agency/api/mcpChatGPT
Settings → Apps & Connectors → Developer mode → Add MCP server → paste the URL.
Same endpoint. Same tools. Same guardrails.
The tools
Five tools. The whole surface.
Read-only today, on purpose. Write scopes ship with Infrastructure.
| Tool | Returns |
|---|---|
| list_plans() | All three plans with flat prices. The agent is $24.98/yr — billed $49.99 once, covers 2 full years, renews at the same $49.99; renewal price equals sticker price. |
| get_state_requirements(state) | New Jersey's requirements: every NJ LLC and corporation needs a registered agent (ours is $24.98/yr, billed $49.99 biennially), and the state's annual report fee is $75. We serve New Jersey only for now, on purpose. |
| recommend_plan(business_stage?, entities?, priority?) | Best-fit plan with reasons — the same logic a human gets at /start. |
| create_signup_link(plan) | A signup URL for agent | command | infrastructure that a human must open and complete. Agents cannot pay. |
| get_service_status() | Live ops metrics: documents scanned today, median scan→briefing seconds, forward-queue depth. |
Guardrails
Your AI can shop. It can't spend.
Agent commerce only works if the human stays in control.
Humans pay, agents prepare
create_signup_link returns a URL a person must open and complete. Agents can't create accounts or submit payment — enforced server-side, not by a prompt.
Prices are server-side
Every price comes from one file on our servers. There is no negotiation surface — an agent can't talk its way to a discount that doesn't exist.
Every call is logged
Tool, arguments, client, and outcome are written to an audit trail the account owner can review. Agent traffic leaves fingerprints.
Rate-limited
30 read calls per minute per client, 5 signup links. Misbehaving agents get slowed down, not served.
Try it from a terminal
One curl away.
Request
curl -X POST https://gardenstate.agency/api/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": { "name": "list_plans", "arguments": {} }
}'Response · truncated
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"structuredContent": {
"summary": "Three flat plans…",
"plans": [
{ "key": "agent", "price_usd_per_year": 24.98,
"price_note": "$24.98/yr — billed $49.99 biennially" },
{ "key": "command", "price_usd_per_year": 190,
… },
{ "key": "infrastructure", … }
]
}
}
}No API key needed for reads. Watch your calls land on the public ops board.
Zapier
Prefer no code? Catch our events in a Zap.
Create a Zap that starts with a “Webhooks by Zapier” trigger (Catch Hook). Paste the catch-hook URL into the ZAPIER_WEBHOOK_URL environment variable on your deployment. From then on, every new scan, signup, and order fires an event to your Zap with the JSON shape { event, ...fields, sentAt }.
Roadmap
The read surface is free and open. The write surface — your AI acting on your own mail — is what Infrastructure buys.