Your agent searches the web and reads any page for $0. When the free call comes back empty or blocked, Relvo tries the next vendor, so your agent still gets pages, sites, social posts, store listings and reviews, all through one API. One key, no extra tool subscriptions.
Compose the request, copy the prompt, and run it in the agent you already use. The price is shown before the call.
The run, step by step: every call goes through one key, priced before it is made.
Your agent asks for a job, not a vendor. Relvo tries the vendors behind that job in order of hit rate, price and speed, and stops at the first real answer. A vendor that bills per success costs nothing when it misses.
Options ride as headers, never in the body, so the call stays the vendor's own request.
Platform data comes back as fields, not a page of HTML: fewer tokens for your agent, and nothing to fix when the site is redesigned.
Pick the client you use, then pick a route: Automatic is that client's own link, command or prompt, and Manual is the same install done by hand. Both end at the same OAuth sign-in, with every tool behind this run reachable through one connector.
Open the plugin page with the details ready.
ChatGPT takes custom MCP servers as plugins. The button opens the right page; copy the name and URL into the form and authorise once.
On the plugins page, click + and choose Add custom MCP server.
Relvohttps://app.relvo.si/mcpPick OAuth, tick the confirmation and click Create as a plugin. Approve Relvo in the browser window ChatGPT opens.
Using Relvo, read https://stripe.com/pricing and return the plans as fields; if the free route comes back empty, let the waterfall try the next vendor and tell me which one answered. Show me the price before the call, then call it.The client inspects the providers behind this run and their prices before the call.
Custom MCP servers are set up in ChatGPT on the web, not in the mobile app. Connect once and every chat can call Relvo.
Set it up from ChatGPT's settings.
The same connector, reached through the settings menu instead of the plugin page.
In ChatGPT, open Settings → Apps & Connectors and create a new custom connector.
Relvohttps://app.relvo.si/mcpChoose OAuth, continue, and approve Relvo in the browser. ChatGPT saves the connector to your account.
Using Relvo, read https://stripe.com/pricing and return the plans as fields; if the free route comes back empty, let the waterfall try the next vendor and tell me which one answered. Show me the price before the call, then call it.The agent checks the providers and their prices, then relays the chosen provider's response verbatim.
https://api.relvo.siSend a project API key as a Bearer token, get a free quote with POST /tools/quote, then run the tool. Using the HTTP API in the documentation walks through each step.
This run draws on the same prepaid balance as the rest of the catalog, at Relvo's published rate. A registered provider key is used instead, and those calls are never metered.
One link fills in the dialog.
On a desktop browser this opens Claude's Add custom connector form with Relvo's name and MCP URL already in place. Click Add and sign in — there is nothing to type.
Click the button above in the browser where you are signed in to Claude. Customize → Connectors opens with the custom-connector form ready.
Click Add, then choose Sign in now under Authentication. Relvo signs you in over OAuth, so no token or API key is pasted into Claude.
Using Relvo, read https://stripe.com/pricing and return the plans as fields; if the free route comes back empty, let the waterfall try the next vendor and tell me which one answered. Show me the price before the call, then call it.The client inspects the providers behind this run and their prices before the call.
The same connector, typed by hand.
Use this on a phone, in a locked-down workspace, or whenever you would rather add the connector through Claude's own menu.
In Claude, go to Customize → Connectors and choose + Add → Add custom connector.
Relvohttps://app.relvo.si/mcpClick Add, choose Sign in now under Authentication, and approve Relvo in the OAuth window. The Relvo tools appear under the connector.
Using Relvo, read https://stripe.com/pricing and return the plans as fields; if the free route comes back empty, let the waterfall try the next vendor and tell me which one answered. Show me the price before the call, then call it.The agent checks the providers and their prices, then relays the chosen provider's response verbatim.
https://api.relvo.siSend a project API key as a Bearer token, get a free quote with POST /tools/quote, then run the tool. Using the HTTP API in the documentation walks through each step.
This run draws on the same prepaid balance as the rest of the catalog, at Relvo's published rate. A registered provider key is used instead, and those calls are never metered.
One command, then one sign-in.
The CLI registers Relvo with HTTP transport and writes it into your Claude Code config; authentication happens in the browser.
claude mcp add --transport http relvo https://app.relvo.si/mcpOpen a session and run /mcp. Choose Relvo → Authenticate; Claude Code opens Relvo's OAuth page and stores the token for the project.
claude mcp listRelvo shows as connected, with every catalog tool behind it.
Using Relvo, read https://stripe.com/pricing and return the plans as fields; if the free route comes back empty, let the waterfall try the next vendor and tell me which one answered. Show me the price before the call, then call it.The client inspects the providers behind this run and their prices before the call.
The command uses local scope by default. Add --scope user to make Relvo available in every project, or --scope project to share it through the repository.
Write it into .mcp.json.
Project scope lives in a file, so the whole team gets Relvo without running a command.
{
"mcpServers": {
"relvo": {
"type": "http",
"url": "https://app.relvo.si/mcp"
}
}
}Create .mcp.json in the project root and add relvo as an HTTP server.
Start a Claude Code session, run /mcp, choose Relvo → Authenticate, then reload. The tools are available in that project.
Using Relvo, read https://stripe.com/pricing and return the plans as fields; if the free route comes back empty, let the waterfall try the next vendor and tell me which one answered. Show me the price before the call, then call it.The agent checks the providers and their prices, then relays the chosen provider's response verbatim.
https://api.relvo.siSend a project API key as a Bearer token, get a free quote with POST /tools/quote, then run the tool. Using the HTTP API in the documentation walks through each step.
The same entry works for every project when it is added at user scope instead of project scope. This run draws on the same prepaid balance as the rest of the catalog, at Relvo's published rate. A registered provider key is used instead, and those calls are never metered.
Hand the setup to Hermes.
Hermes can edit its own config, so one instruction is enough: it writes Relvo into mcp_servers, reloads, and reports the tools it can now call.
Add Relvo as a remote MCP server named "relvo": url https://app.relvo.si/mcp, auth oauth. Follow https://app.relvo.si/SKILL.md, reload MCP, then list the Relvo tools.Hermes adds the remote server to ~/.hermes/config.yaml and reloads its MCP connections.
Open the OAuth link Hermes prints and approve Relvo once. The token is cached, so later sessions do not ask again.
Using Relvo, read https://stripe.com/pricing and return the plans as fields; if the free route comes back empty, let the waterfall try the next vendor and tell me which one answered. Show me the price before the call, then call it.The client inspects the providers behind this run and their prices before the call.
Add it to ~/.hermes/config.yaml.
Two settings and one reload — the same entry Hermes would write itself.
Edit ~/.hermes/config.yaml, the file Hermes reads at start-up.
mcp_servers:
Relvo:
url: https://app.relvo.si/mcp
auth: oauthIn a session, run /reload-mcp, then approve the OAuth prompt Hermes shows. Tokens are cached under ~/.hermes/mcp-tokens/.
Using Relvo, read https://stripe.com/pricing and return the plans as fields; if the free route comes back empty, let the waterfall try the next vendor and tell me which one answered. Show me the price before the call, then call it.The agent checks the providers and their prices, then relays the chosen provider's response verbatim.
https://api.relvo.siSend a project API key as a Bearer token, get a free quote with POST /tools/quote, then run the tool. Using the HTTP API in the documentation walks through each step.
This run draws on the same prepaid balance as the rest of the catalog, at Relvo's published rate. A registered provider key is used instead, and those calls are never metered.
Hand the install to Cursor.
The button opens Cursor's MCP install dialog with the server name and URL already attached.
Click the button on the machine where Cursor is installed. Cursor receives a server named relvo pointing at https://app.relvo.si/mcp.
Confirm the install, then click Authenticate. Cursor completes Relvo's OAuth in the browser.
Using Relvo, read https://stripe.com/pricing and return the plans as fields; if the free route comes back empty, let the waterfall try the next vendor and tell me which one answered. Show me the price before the call, then call it.The client inspects the providers behind this run and their prices before the call.
The install link opens Cursor directly, so it does nothing in a browser that has never installed the editor.
Edit ~/.cursor/mcp.json.
Use the global or the project file when you want the entry under your own control.
Edit ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside the repository for one.
{
"mcpServers": {
"relvo": {
"url": "https://app.relvo.si/mcp"
}
}
}Save the file and reload the window. Relvo appears in the MCP panel, and Authenticate finishes the sign-in.
Using Relvo, read https://stripe.com/pricing and return the plans as fields; if the free route comes back empty, let the waterfall try the next vendor and tell me which one answered. Show me the price before the call, then call it.The agent checks the providers and their prices, then relays the chosen provider's response verbatim.
https://api.relvo.siSend a project API key as a Bearer token, get a free quote with POST /tools/quote, then run the tool. Using the HTTP API in the documentation walks through each step.
This run draws on the same prepaid balance as the rest of the catalog, at Relvo's published rate. A registered provider key is used instead, and those calls are never metered.
Ask the Bot to wire it up.
Grok Bot configures connections from the conversation, so the quickest route is a single instruction with Relvo's address.
Add a custom MCP server called relvo at https://app.relvo.si/mcp with OAuth sign-in, then list the Relvo tools.The Bot repeats the server name and URL and asks you to confirm. Check them and select Add it.
Select Authorize on the card the Bot sends and approve Relvo in the browser once. The Bot can then call the catalog from any chat.
Using Relvo, read https://stripe.com/pricing and return the plans as fields; if the free route comes back empty, let the waterfall try the next vendor and tell me which one answered. Show me the price before the call, then call it.The client inspects the providers behind this run and their prices before the call.
Name the server yourself in the chat.
Grok Bot's settings have no field for a server URL; custom MCP servers are added from the conversation.
Relvohttps://app.relvo.si/mcpAsk the Bot to add a custom server with this name and URL. Say custom server, or it may offer a catalog plugin instead.
The Bot repeats the name and URL. Check that the URL is https://app.relvo.si/mcp, then select Add it.
Select Authorize on the card the Bot sends, sign in and allow access. The Relvo tools appear once you are signed in.
Using Relvo, read https://stripe.com/pricing and return the plans as fields; if the free route comes back empty, let the waterfall try the next vendor and tell me which one answered. Show me the price before the call, then call it.The agent checks the providers and their prices, then relays the chosen provider's response verbatim.
https://api.relvo.siSend a project API key as a Bearer token, get a free quote with POST /tools/quote, then run the tool. Using the HTTP API in the documentation walks through each step.
This run draws on the same prepaid balance as the rest of the catalog, at Relvo's published rate. A registered provider key is used instead, and those calls are never metered.
One access layer in front of the provider's own API — priced per call, with the provider's response passed back as it is.
The same token calls every platform in the catalog.
Relvo's published rate, shown before the call.
Eligible tools run on Relvo's key.
Register a provider key and Relvo uses it instead.
Pick the client you already use. Every one reaches the same catalog through one Relvo key.
The pages this run leans on, in the same catalog and on the same key.
Short answers about the key, the price and the call itself.
One token, one prepaid balance, no provider signup — priced per call, quoted before it runs.
