Botpaid is a hosted MCP server for pay-as-you-go AI media generation.

Quickstart

1. Add the hosted MCP endpoint https://app.botpaid.com/mcp to your MCP client.
2. Sign in with GitHub or Google at https://app.botpaid.com.
3. Add credits starting at $1.
4. Call Botpaid tools like generateImage, generateVideo, or generateAudio.

Machine-readable entry points

• llms.txt for product summary and agent guidance.
• pricing.md for a crawlable pricing summary.
• openapi.json for the hosted MCP transport and public REST surface.
• API catalog for RFC 9727 discovery.
• MCP manifest and server card for transport discovery.

Authentication and access

Protected routes currently use browser session cookies or the hosted MCP OAuth flow on app.botpaid.com. Users authenticate with GitHub or Google. Botpaid does not expose a public API-key-only onboarding flow yet, so autonomous integrations should prefer the MCP endpoint or an authenticated browser session.

{
  "mcpServers": {
    "com.botpaid.mcp": {
      "url": "https://app.botpaid.com/mcp",
      "type": "http",
      "version": "1.3.0"
    }
  }
}

Rate limits and errors

Botpaid returns structured JSON errors for API routes and exposes standard throttling headers on rate-limited endpoints. When a route is throttled, expect 429 with Retry-After, X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset.

curl -i https://app.botpaid.com/status

curl -i https://app.botpaid.com/api/status/REQUEST_ID

curl -i -X POST https://app.botpaid.com/api/checkout \
  -H "Content-Type: application/json" \
  -d '{"amount":10}'

Code examples

const res = await fetch("https://app.botpaid.com/api/status/REQUEST_ID");
const status = await res.json();
console.log(status.status, status.modelName);

import requests

status = requests.get("https://app.botpaid.com/api/status/REQUEST_ID").json()
print(status["status"], status.get("modelName"))

Pricing and webhooks

Use /pricing or /pricing.md for prepaid balance details, example output costs, and the service-fee model. Use /webhooks for Stripe webhook coverage, security expectations, and local testing guidance.