For providers
Turn your REST API into a service agents can buy.
Keep your API and your authentication. Upload an OpenAPI document, set prices per endpoint, and Clankerbay handles discovery, the CLI, MCP tools, metering, billing and monthly payouts.
paths:
/search:
get:
operationId: searchWeb
x-cli-command: search
x-clankerbay-price: 2
summary: Search the web
parameters:
- name: q
in: query
required: true
schema: { type: string }
Register
Create a provider profile and a service namespace, e.g. acme-weather. Set your upstream base URL.
Describe
Upload OpenAPI 3.0 or 3.1. We validate it, preview the generated commands and flag breaking changes between versions.
Price & secure
Price each endpoint in credits. Store the API key or token the gateway should use; it is encrypted at rest and never shown to consumers.
Earn
After review your service goes live. Watch requests, success rates and latency, and cash out monthly earnings.
Earnings
How you get paid
Each successful call earns you the credits your endpoint charges. Earnings are tracked separately by the kind of credit the consumer spent, and settled once a month:
- Prepaid credits are valued at the price the consumer paid for them, using the exact package rate recorded with each credit allocation.
- Subscription credits share the month's subscription revenue pool (net of taxes, payment fees and refunds), in proportion to the subscription credits actually spent across the marketplace.
A platform fee of 20% is deducted from gross earnings. The remainder is added to your available balance, which you can cash out once it reaches €20.00. Cashouts are reviewed by an administrator and paid through Stripe Connect.
Worked example · subscription pool
Eligible subscription revenue this month: €300
If your endpoints earned 60 of 300 subscription credits, your gross subscription earnings are 60 × €1.00 = €60.00, before the 20% platform fee.
Unused subscription credits are never paid out: only credits earned through actual calls take part. If no subscription credits are spent in a month, the pool is not distributed.
Your auth, untouched
Consumers authenticate to Clankerbay. The gateway authenticates to you with the header, bearer token, query key or basic auth you configure.
Versioned, reviewed changes
Schema versions are validated and reviewed. Prices and credentials are versioned and audited, so consumers are never charged more than they expect.
Real monitoring
Request volume, success and failure counts, status codes, p50/p95/p99 latency and last successful call, per endpoint.