Quick Start — Intent Infra

For agents and their operators: connect to the hosted platform, fund an account, and receive verified infrastructure on your own AWS account — unaided, in one session. A free sandbox (mock infrastructure) requires no AWS account and no payment.

Local development setup: see docs/CONTRIBUTING.md and HANDOFF.md.

1. Connect

MCP (recommended — 11 tools)

Add the remote MCP server to your client config:

// opencode.json / claude_desktop_config.json / cursor mcp.json
{
  "mcp": {
    "infra-execution-layer": {
      "type": "remote",
      "url": "https://api.intent-infra.com/mcp",
      "headers": { "Authorization": "Bearer <token from step 2>" }
    }
  }
}

initialize and tools/list work without a token — point a client at /mcp and inspect the tools before signing up.

REST

Base URL: https://api.intent-infra.com/api/v1 · OpenAPI 3.1: GET /openapi.json · Agent card: GET /.well-known/agent.json · Manifest: GET /api/v1/capabilities (unauthenticated) · Human docs: GET /llms.txt

2. Sign up (self-serve, free)

curl -X POST https://api.intent-infra.com/auth/tokens \
  -H 'content-type: application/json' \
  -d '{"agentId": "my-agent", "scopes": []}'
# → { "token": "...", "nextSteps": { ... } }

The response includes nextSteps — follow them to continue unaided.

3. Sandbox: zero-to-first-deployment (free, no AWS account)

The public sandbox at https://sandbox.intent-infra.com runs mock infrastructure with free billing — the full flow works end to end with no token, no AWS account, and no payment. Swap the host in any example (sandbox.intent-infra.com instead of api.intent-infra.com) or use the sandbox MCP endpoint https://sandbox.intent-infra.com/mcp.

# Free sandbox credits
curl -X POST https://sandbox.intent-infra.com/api/v1/billing/topup/sandbox \
  -H 'content-type: application/json' -d '{"amountUsd": 25}'

# Tier options with monthly provider estimates (free)
curl -X POST https://sandbox.intent-infra.com/api/v1/suggestions \
  -H 'content-type: application/json' \
  -d '{"outcome": "deploy a production web application", "region": "us-east-1"}'

# Quote (sandbox: free). Responses are labeled "sandbox": true.
curl -X POST https://sandbox.intent-infra.com/api/v1/quote \
  -H 'content-type: application/json' \
  -d '{"outcome": "deploy a production web application", "region": "us-east-1", "tier": "starter"}'

# Deploy — mock infrastructure, fee waived
curl -X POST https://sandbox.intent-infra.com/api/v1/deployments \
  -H 'content-type: application/json' -d '{"quoteId": "q-..."}'

# Poll until status=active (verification results + terraform files included)
curl https://sandbox.intent-infra.com/api/v1/deployments/d-...

4. Real deployments

1. Top up — agents: POST /api/v1/billing/topup/xrp {amountUsd} (XRP testnet deposit, credited on confirmation). Humans: POST /api/v1/billing/topup/stripe {amountUsd} (Checkout URL).
2. Connect your AWS account — least-privilege IAM template and encrypted credential upload: docs/AWS_CREDENTIAL_SETUP.md.
3. Run the same flow as the sandbox. Watch for:
   • HTTP 402 — insufficient credits; the body contains machine-readable top-up instructions. Top up and retry.
   • maxMonthlyCostUsd — pass your monthly cost cap at suggest/quote/deploy; options above the cap are filtered or rejected with MAX_COST_EXCEEDED.
   • Failed = free — the deploy fee is captured only after verification passes; it is released automatically on failure.

Pricing (platform fees)

Provider costs bill to your own cloud account — quotes display provider estimates for transparency only.

Troubleshooting

• 401 on tool calls — token missing/invalid; MCP initialize works without one. Re-run step 2.
• 402 insufficient_credits — top up (step 4); the error body lists both rails.
• stripe_not_configured (503) — this deployment has no Stripe account yet; use the XRP rail.
• Deployment failed — no charge (hold released). The status payload includes the Terraform error translated to an agent-readable hint.
• Support — escalation contact is included in error payloads.