re:solved developer resources

re:solved API & MCP Server Documentation

Everything an agent or developer needs to work with re:solved digital: the machine-readable OpenAPI specification, the public intake API, our MCP server, and the discovery files that describe this site.

Quick links

/openapi.json — OpenAPI 3.1 specification
/.well-known/api-catalog — RFC 9727 API catalog
/api/public/versions — versioning & deprecation policy
/llms.txt — site summary for language models
/.well-known/ai.txt — AI usage directives
/sitemap.xml — all public pages
/rss.xml — blog feed

Endpoints

Method	Path	Auth	Description
GET	/openapi.json	None	OpenAPI 3.1 specification for the whole public surface (alias: /api/openapi.json).
POST	/api/public/v1/ai-audit-submit	None	Submit an AI Automation Opportunity Report request (version-pinned). JSON in, JSON out.
POST	/api/public/ai-audit-submit	None	Permanent unversioned alias of the current major version (v1).
GET	/api/public/versions	None	Machine-readable API versioning and deprecation policy.
GET	/.well-known/api-catalog	None	RFC 9727 linkset pointing at the OpenAPI spec, docs and version metadata.
POST	/mcp	OAuth 2.1	re:solved MCP server (Streamable HTTP). Tools: get_services_and_pricing, list_blog_posts, search_blog_posts, get_blog_post.
GET	/.well-known/oauth-protected-resource	None	OAuth protected-resource metadata for the MCP server.
GET	/llms.txt	None	Site summary for language models.
GET	/.well-known/ai.txt	None	AI crawling, training and attribution directives.
GET	/sitemap.xml	None	Sitemap with hreflang alternates.
GET	/rss.xml	None	Blog RSS 2.0 feed.

Authentication

The public HTTP endpoints listed above require no credentials. The MCP endpoint (/mcp) is protected with OAuth 2.1; clients discover the authorization server from /.well-known/oauth-protected-resource and complete a standard authorization-code flow with PKCE. Most MCP clients handle this automatically once you add the server URL.

Example request

curl -X POST https://re-solved.digital/api/public/v1/ai-audit-submit \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Ada Lovelace",
    "email": "ada@example.com",
    "company_name": "Example GmbH",
    "biggest_manual_task": "Manual quotation preparation",
    "consent_to_contact": true
  }'

# 200 OK
{ "ok": true }

Error format

Every /api/* failure returns JSON with a stable error code, a human-readable message, a recovery hint, and links back to these docs.

{
  "error": {
    "code": "invalid_request",
    "message": "Name, company name and a valid email are required.",
    "hint": "Send name, email and company_name as non-empty strings.",
    "status": 400,
    "docs": "https://re-solved.digital/developers",
    "openapi": "https://re-solved.digital/openapi.json"
  }
}

MCP server

Add the re:solved MCP server to any MCP-compatible client to query our services, pricing and guides directly:

{
  "mcpServers": {
    "re-solved": {
      "url": "https://re-solved.digital/mcp"
    }
  }
}

re:solved API versioning & deprecation policy

The re:solved API uses URL path versioning. The canonical form is /api/public/v1/<endpoint>; the current major version is v1. Unversioned paths such as /api/public/ai-audit-submit are permanent aliases of the current major version — pin the versioned path for production integrations.

Every API response carries API-Version and API-Supported-Versions headers.
Breaking changes never land in an existing version. They ship under a new path (for example /api/public/v2/…).
Additive, backwards-compatible changes (new optional fields, new endpoints) may ship in the current version at any time.
Endpoints scheduled for removal respond with Deprecation: true, a Sunset date (RFC 8594) and Link: <…/developers#versioning>; rel="deprecation" for at least 180 days before the endpoint is withdrawn.
The policy is machine-readable at /api/public/versions and mirrored in the x-versioning extension of the OpenAPI document.

Webhooks

re:solved does not currently publish outbound webhooks. Agent deployments we operate for clients are wired to their own systems during onboarding — write to contact@re-solved.digital to discuss an integration.