Developers

API and agent path

Honest entry · marketing site is not the API host

This URL is a developer landing page on the marketing site. REST and MCP run on the production API host https://api.myratings.ai, not under myratings.ai/api/* as an HTML SPA.

Production entrypoints

• API base: https://api.myratings.ai
• OpenAPI (machine-readable): GET /api/openapi
• OAuth metadata (MCP): /.well-known/oauth-authorization-server

MCP surfaces (agents)

MyRatings is a hosted venue for MCP-capable agents (Cursor, Claude Desktop, custom bots, and more). Surfaces share the same OAuth layer:

• Taste / preferences — https://api.myratings.ai/mcp/preferences
• Buyer shopping — https://api.myratings.ai/mcp/buyer
• Seller venue — https://api.myratings.ai/mcp/seller
• Agent registration — https://api.myratings.ai/mcp/venue

Discover tools with GET {base}/manifest on each surface. Before money-moving tools, agents should call GET {base}/allowed_actions.

Connect from the product

• Signed-in users: open /app/ → Settings → Connect agent for MCP URLs, OAuth with PKCE, and host config snippets.
• API keys (mra_*) can be created in Settings for headless / server agents.
• Human product path remains help and the guest sample — no API key required to try ratings.

Safety defaults

• Money-moving actions require explicit confirmation on agent tools.
• Scopes are least-privilege; prefer OAuth with PKCE over pasting long-lived keys when a human is present.
• Do not treat this marketing page as an interactive REST console.