Developers and agents

AutoRFP.ai API and MCP documentation

Build on AutoRFP.ai with the REST API, or connect AI assistants and your own agents through the MCP server.

Start here

Pick the path that fits

  • Base URLs by region, the response format and your first request.

  • Create an API key, choose its scopes and keep it safe.

  • Every endpoint for projects, content, tags, teams and your organisation, with request and response examples.

  • Connect Claude, ChatGPT or Cursor, or call the MCP server from your own agent.

  • The REST API as an OpenAPI document, to generate a client or import it into your tools.

  • Read-only JSON about AutoRFP.ai itself, with no credentials. It does not return workspace data.

RegionREST APIMCP server
AUhttps://api.autorfp.ai/v1https://api.autorfp.ai/mcp
UShttps://api.us.autorfp.ai/v1https://api.us.autorfp.ai/mcp
EUhttps://api.eu.autorfp.ai/v1https://api.eu.autorfp.ai/mcp

A small read-only API describes AutoRFP.ai the company: name, links, and where to find the MCP server. It needs no account and returns no workspace data. Unknown /api/* paths return HTTP 404 asapplication/problem+json.

For agent builders

Machine-readable discovery files

Clients and crawlers read these to find the server and its sign-in details on their own. You rarely need to open them by hand.

Next step

See what better answers look like on your RFP.

  1. [01]A 45 minute walkthroughBuilt around the questionnaires your team answers today, not a generic demo.
  2. [02]A free two-week proof of conceptProve it on your own RFPs, with your content and your reviewers.
  3. [03]First answers, cited to your contentAI-drafted answers in as little as 48 hours of bringing your content in.