rebilly.com
Rebilly provides payment orchestration, subscription billing, KYC, and related transaction workflows for merchants. Its platform lets businesses manage payments, customer billing, risk, and integrations through hosted and API-based tools.
Rebilly exposes a REST API for payments/billing operations and an MCP server; the REST API supports secret API keys, JWTs, and limited publishable-key use, while the MCP server uses OAuth 2.0 with dynamic client registration.
- Rebilly REST APIdiscovered
In the Rebilly app, go to API keys. Under Automations → Development → API keys, click Create API key, choose Secret, save it, then copy the key from the Key column. The API docs say server-side requests use the secret key in the REB-APIKEY header, and requests should include the organization in the URL path such as /organizations/{organizationId}/....
Rebilly's OpenAPI description lists JWT as a supported authentication method for the REST API, describing it as a short-lifetime token with a specific expiration time. The public docs scraped here do not show a self-service minting flow for developers, so use the Rebilly developer docs and account/app features to obtain or issue a JWT for your integration as supported by your account.
conventions · 2/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✓https://rebilly.com/llms.txt
- API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✓https://rebilly.com/.well-known/oauth-protected-resource
- Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing