mocop
Browse · Docs · Guide · Analyze

Automo Build API

API by Automo · rest

The machine surface of Automo Build, the AI app builder. All capability calls go through the MCP endpoint (Model Context Protocol, Streamable HTTP): tools are discovered live via tools/list after OAuth sign-in. This document describes that endpoint, the OAuth 2.1 authorization server that protects it, and the discovery documents around them. Start at the server card or the protected-resource metadata; the site overview for agents is https://automo.build/llms.txt; agent registration is walked through at https://automo.build/auth.md. Rate limits: the unauthenticated endpoints answer with RateLimit-Policy, RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset (seconds), counted per client IP. MCP tool calls carry the same headers for the connection's read, write or spawn budget. Past the limit the answer is 429 with Retry-After. Idempotency: POST /agent/identity accepts an Idempotency-Key header (16 to 255 printable characters, a UUID is ideal). A retry with the same key and body…

Endpoint: https://mcp.automo.build/

Verification: observed. Source: crawl.

Capabilities (13)

  • JWKS for access-token verification
  • MCP server card
  • RFC 8414 authorization-server metadata
  • RFC 9728 protected-resource metadata
  • Security event receiver for agent providers (RFC 8935)
  • Register an agent for its user (auth.md)
  • Restart the claim ceremony with a fresh code
  • The MCP endpoint (Streamable HTTP)
  • OAuth 2.1 authorization endpoint
  • RFC 7009 revocation endpoint
  • OAuth 2.1 token endpoint
  • This document
  • RFC 7591 dynamic client registration (public clients)
About · Contact · Privacy