List your API in the Relvo catalog
Send the API, its docs and a way to reach your team. We check it against the requirements below, run real calls at your published price, and add the endpoints to the catalog with what each one costs.
Read the requirements first
The same checklist applies to every provider, whatever its size or category.
Confirm eligibility first. Hard requirements: self-serve API keys (no sales call), the key rides in a header or query param (never the URL path), a free or near-free probe endpoint that rejects an invalid key with a distinguishable response, a published pricing page, and docs with example parameter values.
If any of those is missing, say so in your message — a provider that fails one item can still be listed once it is fixed, but we cannot price a call we cannot verify.
One message with everything below
A complete listing can be reviewed in a single pass; a partial one costs a round trip.
- The provider. Service slug, display name, base URL, auth mechanics, category, a one-line summary and the URL of your docs.
- The probe. One cheap endpoint an agent can call to prove a key works, with the response your API returns for an invalid key.
- The endpoints. The 8–15 endpoints an agent would actually reach for, each with a capability, typed input parameters, a cheap test request and the cost with its source (your pricing page or rate card).
- The mark. A square logo file, or permission to use the one on your site.
- A contact. An email for the team, so we can arrange a test credential and send the published listing.
Reuse before you propose
Capabilities are how an agent compares providers, so overlap is the point — not a duplicate.
For every endpoint, before naming its capability:
- Reuse. Search the catalog for the job it does. If a capability exists, use that id rather than inventing a near-synonym.
- Propose only when missing. If another provider already has an endpoint doing the same job but no capability covers it, propose one and name that endpoint in your message.
- Prefer overlap. Endpoints sharing a capability are the ones agents compare and route between, which is what makes the listing useful.
Run every test request with your own key
Docs drift; meters don't. The price you send should be the price the account was actually charged.
Before you send the listing, run every test request live against your own account and reconcile each cost against what the meter charged. Say which environment, region or plan the price applies to, and the date you checked it.
Send example responses only where they are public in your docs. Never put a credential value anywhere in the message.
Review, live test, publish
Every listing goes through the same live check before it appears in the catalog.
We call the probe endpoint with a real key and with a bogus one, confirm the two responses are distinguishable, and reconcile the quoted costs against the meter. If something does not match, we reply with the exact call that failed.
Once it passes, the provider gets its own page under Tools and its endpoints get their catalog pages, each priced per call at your published rate. Write to info@relvo.si to start.