Wallet sign-in
Sign in with an authorized wallet.
Connect your agent.
Connect your existing agent to OpenAny resources.
Your agent
01Prepare access
Keep OPENANY_API_KEY in the client environment or private secret settings. Never paste the key into a prompt or this page.
02Configure your client
- MCP server
https://mcp.openany.si/mcp- Transport
- Streamable HTTP
- Authentication
Authorization: Bearer <OPENANY_API_KEY>
No OAuth. Tool discovery is public; executing a resource requires your OpenAny key and spending authorization.
.mcp.json
{
"mcpServers": {
"openany": {
"type": "http",
"url": "https://mcp.openany.si/mcp",
"headers": {
"Authorization": "Bearer ${OPENANY_API_KEY}"
}
}
}
}Merge this entry into existing settings. Make the environment variable available to the client process, then reload its MCP configuration. Client-specific paid calls have not been verified by this page.
Client documentation03Verify one bounded task
Reload your client and inspect the OpenAny tool list. Discovery alone does not verify a paid request. Inspect the tool schema and price before approving one task.
Live verification pending
Agent instructions & reference files
01 / ACCESS
One key, in your agent's environment.
Create a key and make it available to the process that runs your agent. Keep its value in an environment variable or the client's secret store.
Environment and billing reference
- API base URL
https://api.openany.si/v1- API key
OPENANY_API_KEYCreate a key- Authentication
Authorization: Bearer <your key>- Shared balance
- Review card, USDC and x402 funding options.Add credits
Your agent can check whether a key exists without displaying it. Enter secrets through your environment or secret manager, rather than the setup prompt.
Manual text API reference
Choose an available Chat Completions model from the catalog. Replace MODEL_ID_FROM_LISTING in cURL, or set OPENANY_MODEL for the Python and Node.js examples. Model IDs are route-specific; do not assume a historical example is still available.
02 / VERIFY
Make the first call.
These are manual SDK examples for a text Chat Completions test. Verify the current model ID, operation and price first. Agents using SKILL.md should use models run with the published operation and parameters.
Requires cURL and OPENANY_API_KEY in the shell environment. Check model listing
curl - Chat Completions
curl --fail-with-body --silent --show-error \
https://api.openany.si/v1/chat/completions \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "MODEL_ID_FROM_LISTING",
"messages": [{
"role": "user",
"content": "Reply with exactly: OpenAny connected"
}],
"max_tokens": 32
}'What success looks like
A successful response has HTTP 2xx and non-empty choices[0].message.content. Inspect usage when returned, then review your usage records. Usage records
Configuration alone is not verification. If a live call has not run, report: "Configured; live verification pending."
03 / USE
Start with the resource your task needs.
Open the market, select a listing, and read its current schema and price. Each resource has its own delivery mode.
Use the model's published protocol and operation.
- Copy the exact API model ID from its listing.
- Use the base URL and Bearer key above with the documented endpoint.
- Choose an available provider route or use an existing dashboard routing policy where supported.
- Return the model output and the usage fields received.
For a provider override, copy the request schema from the model’s API tab. For a saved route, use its actual route:id where supported.
Browse model APIsDetailed CLI recipe
04 / CLIENT GUIDES
Connect from your agent.
Install the OpenAny skill and matching CLI for resource calls. These recipes keep your agent's existing main-model configuration.
Claude Code
Install the OpenAny skill and use the latest published CLI for model, data, and tool API calls in the existing agent environment.
SKILL LOCATION
.claude/skills/openany/SKILL.md- Review AGENT.md and SKILL.md, then save the skill at .claude/skills/openany/SKILL.md. Refresh skills or start a new session as the client requires.
- Use Node.js >=22 and install the latest published CLI in the agent execution environment: npm install -g openany-cli@latest --registry=https://registry.npmjs.org/. Check openany --version and openany --help. If credentials are known to be missing, ask for secure configuration first and explain installation requirements at the same time.
- Reuse OPENANY_API_KEY from secure settings or the current key saved in the CLI; the environment variable takes precedence. Ordinary calls do not require wallet/email login. Never scan repositories, .env files, user directories, or credential stores for keys. Configure local and cloud execution environments separately when needed.
- Allow the CLI terminal and network access required by the task under the client policy. The built-in service and signing domain is https://openany.si and the API gateway is https://api.openany.si; they cannot be overridden at runtime.
- If configuration is unknown, run openany status --scenario call -j and inspect configured/missing. Pause if credentials are missing; on an API-key 401 ask the user to check that key. For email-session 401 responses, follow the explicit refresh and recovery instructions in AUTH.md without switching domains. A successful local check alone does not verify API access.
- Use the skill for external resource calls through the CLI. Check balance, discover the resource, inspect its current definition, and call only within the approved purpose and budget. For model calls, use the models commands in SKILL.md. Keep the agent main-model configuration unchanged.
Invocation example
Use the OpenAny skill and CLI
Use the openany skill and the latest published CLI for this task. Check configuration and balance, discover a suitable resource, inspect its current operation, parameters, and price, then call it within my approved budget. Ask for missing credentials, permissions, or budget. Report the actual result, request ID, and usage or cost when returned. After a data or tool API timeout, check calls list/get with the same key. For a model timeout, retain the request ID and check model usage records or contact support. Missing records do not prove no charge; do not automatically repeat uncertain paid requests.Verify the connection. Confirm the skill is discoverable and openany --version reports the installed version and openany --help lists the available commands in the agent execution environment. Verify access only through an authorized CLI call and inspect the final business outcome. Installation, a local status check, or HTTP 200 alone is not sufficient. If no call ran, report Configured; live verification pending. See SKILL.md for public-catalog-only access, authentication, top-ups, and recovery.
Other agents need terminal access and Node.js >=22 for this CLI workflow. Use AGENT.md and the client's documented skill directory; an HTTP-only client cannot run these commands.Machine-readable client recipes
Agent sign-in
Authentication reference
Wallet or email. Your agent signs in.
Reuse an authorized credential, or follow a verified authentication contract using an identity you authorize.
Email sign-in
Sign in with an authorized email account.
Wallet sign-in needs an authorized signer. Email sign-in needs the documented verification method and permission to use that identity. Without those permissions, your agent must ask for approval rather than inventing a login flow.
Use AUTH.md for the implemented CLI login and key-management commands. Availability depends on service configuration. Copying instructions alone does not verify login or authorize payments.
05 / PAYMENTS
Fund a balance, or pay an endpoint directly.
Choose the payment flow before execution. Keep all calls inside the budget you give the agent.
MethodAgent accessSettlement
Card top-upOpenAny API keyUsage draws from your shared balance.
USDC top-upOpenAny API key after fundingA transfer funds your shared balance on the specified network.
x402 top-upOpenAny API key after fundingFunds the same shared balance.
Direct x402Compatible wallet or payment clientPer-request payment only at an explicitly supported endpoint.
Manage card, USDC and x402 top-ups, card auto top-up and USDC subscriptions on the Credits page. Available payment routes come from your account service. Review the locked payment quote before authorizing; credits are added after the service confirms payment.
Direct x402 is a separate resource-specific integration, outside the CLI workflow documented here. Do not interpret a CLI API-call 402 as permission to bypass API-key billing or create a payment proof.
Return the actual usage and charge when available. When the response omits cost, link to usage records instead of estimating a settled receipt.
Payments & fees
Payment methods, costs and what to check before adding credits.
How can I pay?
Add credits on the Credits page by credit card, USDC transfer or x402. All three fund the same shared balance. Account-based API calls use your OpenAny key after funding. Direct x402 is a separate per-request flow, only where the endpoint explicitly supports it.
Is there a fee on top-ups?
Check the payment quote for the total charged, credits received, currency and any processing, conversion or network fees before paying. This guide does not publish a universal top-up fee. If quote details are missing, contact support before paying.
Which token and network should I use?
Send funds only to the asset, network, recipient and amount shown in your payment request. USDC and USDT are not interchangeable, and the same token on a different network is not the same payment route. Do not send funds to example addresses.
How do auto top-up and USDC subscriptions differ?
Card auto top-up adds credits when your balance reaches the account's threshold. A USDC subscription adds a fixed amount on a fixed schedule. Each needs its own authorization and can be managed on the Credits page. Available routes and authorization terms come from your account service. A one-time payment or wallet sign-in does not authorize recurring charges. The CLI's user-authorized top-up policy runs inside your agent, not a background subscription service.
I paid, but my balance has not updated. What should I do?
Check the payment status and account before paying again. For a live payment issue, contact support with the payment or order reference, amount, currency and time. For an on-chain payment, include the network and transaction hash. Never send a private key, seed phrase, full card number or API key. Pending or failed payments should not be treated as credited funds.
How are model, API and skill calls charged?
Check the selected provider's published rate and billing unit: text models commonly separate input and output tokens, while APIs and media models may charge by call, image, second or another usage unit. Skills run in your agent and use their underlying models and APIs. Calculator results are estimates; recorded usage determines the charge under the selected route's billing contract.
Are failed or timed-out requests charged?
Do not infer the charge from the HTTP status alone. Check the selected service's billing contract and recorded usage; a timeout does not prove that processing stopped. Verify the request or payment state before retrying, especially for paid or write operations. Local mock calls are not billed. If a recorded charge looks incorrect, share its request reference with support.
Invoices & refunds
Find the right payment records and get help with billing requests.
Can I get an invoice or payment receipt?
Credits shows your top-up history and Usage shows what you consumed. A top-up record, an API usage record and a tax invoice are different documents. For a receipt or invoice, contact [email protected] with the payment reference to confirm what can be provided.
Can I request a consolidated or customised invoice?
Contact support with the relevant payment references, billing period and required company details. Confirm the legal name, billing address and any applicable tax identification before issuance. Availability, invoice format and any tax treatment need confirmation; this guide does not promise automatic consolidation, retroactive changes or a specific jurisdiction's tax invoice.
Can I request a refund?
Contact support before assuming that unused credits or a completed payment are refundable. Include the payment reference and reason, such as a suspected duplicate or incorrect charge. Eligibility, refundable amount, return method and timing need confirmation under the terms applicable to that payment. A failed API call, a cancelled recurring setting or a confirmed blockchain transfer does not itself trigger a refund.
When a connection needs attention.
Use the response to identify the missing step. Retry only when the request is safe to repeat.
400- Check the model ID and required fields against the selected listing.
401 / 403- For API-key requests, check the key and permissions. For an expired email session, follow AUTH.md and explicitly run auth email refresh; refreshing a session does not repair an API key.
402- For CLI resource calls, check balance and the authorized top-up policy. Payment requirements belong to the separate topups flow; do not treat every 402 as a direct resource payment.
404- Check the base URL and protocol. Chat Completions does not imply Responses or Anthropic Messages support.
429- Honor Retry-After and retry with bounded backoff.
5xx / timeout- For data/tool APIs, check calls list/get with the same key. For models, check model usage records or contact support. Missing records do not prove no charge; never automatically repeat an uncertain paid request.
A useful setup report includes the client, setup location, resource ID, test result, available usage, and remaining requirements. Keep credentials out of the report.
Common questions
Can my agent complete setup on its own?
Email and wallet sign-in are available through the OpenAny CLI. Your agent needs an authorized inbox or signer and must follow AUTH.md. It can store the API key it receives without displaying it. Missing authorization must be requested; copying instructions is not successful login.
Does one key work across all resources?
One OpenAny key authenticates supported account-based models and APIs. A portable skill runs inside your agent and uses the credentials of its dependencies. Direct x402 calls use an authorized payment instead of an OpenAny API key.
Do I have to change my agent's main model?
No. The integration skill lets your agent call OpenAny resources through its existing tools. OpenClaw and Hermes can also use a compatible OpenAny model endpoint as their inference provider. A provider switch requires protocol and model capability checks.
Is there an OpenAny MCP URL or CLI to install?
OpenAny provides https://mcp.openany.si/mcp over Streamable HTTP. Tools/list is public; resource execution uses Authorization: Bearer with your OpenAny API key. The MCP server does not use OAuth. Skill and CLI setup is a separate terminal-based path. Check the current resource schema and price before approving a call.
Where do skills execute?
Skills run inside your local agent or its existing hosted environment. OpenAny provides supported model and API dependencies. A skill file alone does not execute a task or establish API access.
How do I know setup worked?
Verify a real authorized request and inspect its response. For Chat Completions, expect an HTTP 2xx response and non-empty choices[0].message.content. Inspect usage and the dashboard where available. If no live test ran, the correct status is configured, verification pending.
Ready for your first task?Explore the market