OPENANY / DOCUMENTATION

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 documentation

03Verify 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.

  1. Copy the exact API model ID from its listing.
  2. Use the base URL and Bearer key above with the documented endpoint.
  3. Choose an available provider route or use an existing dashboard routing policy where supported.
  4. 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 APIs
Detailed 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
  1. Review AGENT.md and SKILL.md, then save the skill at .claude/skills/openany/SKILL.md. Save setup.md, calls.md, and topups.md from the same site alongside it. Refresh skills or start a new session as the client requires.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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 calls.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.

Wallet sign-in

Sign in with an authorized wallet.

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.

SELLER / OPENANY

Seller overview

Sell resources and services. Give agents a result they can use, not just a package they must learn to run.

Sell what it does. Keep how it works.

You can sell templates, but you do not have to stop there. Run a skill or bot in your own environment, connect its endpoint and sell repeatable access to its work. A template can sell to many buyers; a callable service can also serve new paid tasks from the same buyer.

01Buyer agent submits inputs
02OpenAny routes the call
03Your endpoint executes
04Buyer receives the result

Charges follow the configured billing unit and charge conditions, not this diagram. Sellers provide resources or execute services; OpenAny connects the two sides of the transaction.

Template sales and callable services

CompareSell a templateSell callable access
What buyers receiveFiles, instructions or configuration.Access to an operation and its agreed result.
Who runs itThe buyer installs and maintains the environment.You run the agent, tools and endpoint.
Repeat businessA template can be sold to many buyers; each license follows its terms.The same buyer can pay for new tasks or usage again.
Updates and controlBuyers receive and apply template updates.You update the service without distributing the internal workflow.
Costs and responsibilityMaintain the package, license and setup instructions.Also cover execution costs, capacity, security and delivery.

Repeat use is an opportunity, not guaranteed income. Deduct model, tool, server, support and applicable payment or payout costs when judging your margin. Keeping logic server-side does not guarantee that outputs cannot be copied.

Resources: choose a type, manage pricing and inspect publication status.
Resources: choose a type, manage pricing and inspect publication status.Full-size screenshot

Current Seller Console captured with local Mock data. Names, prices and states are examples, not live listings or actual earnings.

Start with one resource

  1. Create your seller profile and complete supplier admission. Review is required once; a saved draft is not admission or publication.
  2. Prepare a service you control, an authorized connection and a precise input/output contract. OpenAny does not host your bot or skill runtime.
  3. Set pricing and charge conditions, save a draft and authorize a bounded test. Verification can incur costs.
  4. Check the buyer-facing preview and publish after the required verification. Publication and runtime readiness are separate states.
  5. Monitor calls and estimated income in Seller Revenue, and confirmed settlements in Payouts. Buyers inspect usage records and available results in Usage.

Instant or asynchronous delivery

Synchronous
The endpoint returns the result in the call response. Use it for work that fits the endpoint timeout.
Asynchronous
The service accepts a task and supplies final results through the configured callback or polling contract. Configure timeout, output and billing explicitly. Acceptance is not completion.
Give this to your agent
Read https://openany.si/docs/#seller-overview and https://openany.si/skills/openany-provider/SKILL.md. Help me prepare a resource or service for sale on OpenAny. Confirm ownership, execution, inputs, delivery, pricing and costs with me. Keep credentials out of chat. Check the current CLI and server schema; if unsupported, stop and explain the console path instead of changing the resource type. Prepare a draft first; get my approval before any paid test or publication.

Copying does not submit, test, publish or authorize spending. An agent must inspect the current seller skill and server schema, use an admitted seller identity and ask for missing permissions.

Sell skills

Sell what your skill does, not just the template. Keep it in your own agent and expose a callable service that returns a useful result.

Benefits, setup and a worked example
TEMPLATE PACKAGE

Deliver a research prompt pack for buyers to install and run.

THROUGH OPENANY

Run the research skill for each buyer request and return a structured brief.

Why sell it this way?

  • New research tasks create new opportunities for paid calls, including from the same buyer.
  • Keep your prompt, source selection and tool chain on your side. Buyers do not have to recreate the setup.

Prepare and publish

  1. Prepare the skill service

    Run the skill in your agent or server. Provide an endpoint you control and confirm you may use its tools and data commercially.

  2. Add Skill and describe the outcome

    In Resources, select Add Skill. Complete the name, categories, description, Overview, Included, How to use and Examples. Describe a result, not an unsupported promise.

  3. Connect and define the request

    Bind an API Key connection. Set the method and call path, required inputs and example responses. Choose synchronous or asynchronous execution to match your endpoint.

  4. Price, test and publish

    Set your rate and charge condition. Save, authorize a bounded test, inspect the result, then review the buyer preview before publishing. Supplier admission is required.

Request: connect your endpoint and define the inputs buyers will send. Parameters are optional when the endpoint needs none.
Request: connect your endpoint and define the inputs buyers will send. Parameters are optional when the endpoint needs none.Full-size screenshot

Current Seller Console captured with local Mock data. Names, prices and states are examples, not live listings or actual earnings.

Pricing and delivery

Fixed per-call billing suits a defined report. Usage billing needs a trustworthy quantity in the response, its JSON Pointer, unit and rounding rules. A successful HTTP status alone does not prove a useful report; configure the appropriate business-success condition.

Short transformations can return directly. Longer research can use the configured async delivery contract. An accepted task is not a completed report.

ILLUSTRATIVE EXAMPLE

Competitor research skill

Buyer inputs
Industry, target region, competitor names and the question to answer.
Your execution
Your agent runs the skill, queries permitted sources and assembles the findings.
Buyer receives
A competitor comparison, source links, a brief and explicit gaps in the evidence.
Billing example
For illustration, USD 0.50 per qualifying call. At 20 qualifying calls, gross charges are USD 10 before execution costs and applicable fees; this is not an earnings forecast.
Repeat use
A buyer returns for a different region, product launch or weekly update.
Scope limits
State the source coverage and update date. Do not promise complete, real-time or legally cleared research.

A callable skill is different from a downloadable skill package. This console configures the service endpoint; it does not install, host or execute your private skill for you.

Give this to your agent
Read https://openany.si/docs/#seller-skills and https://openany.si/skills/openany-provider/SKILL.md. Help me prepare skills for sale on OpenAny. Confirm ownership, execution, inputs, delivery, pricing and costs with me. Keep credentials out of chat. Check the current CLI and server schema for catalog type skill; if unsupported, stop and explain the console path instead of changing the resource type. Prepare a draft first; get my approval before any paid test or publication.

Sell bots

Let buyers use your bot without giving away its entire configuration. Your bot stays in your environment and performs the tasks your listing promises.

Benefits, setup and a worked example
BOT CONFIGURATION

Sell a bot configuration and ask buyers to arrange their own models and tools.

THROUGH OPENANY

Sell a defined task performed by your bot, with clear inputs and deliverables.

Why sell it this way?

  • A buyer can return for a new brief instead of buying and operating a bot stack.
  • Improve the bot centrally and keep your orchestration private, while owning the responsibility to deliver.

Prepare and publish

  1. Make the bot callable

    Prepare a controlled HTTP endpoint or an adapter supported by the current console. A Grok Bot, Muse or other personal agent is usable only if you can connect its trigger and return its final result; a product name is not proof of compatibility.

  2. Define one concrete service

    Choose Add Bot. Explain what it produces, what is excluded, the required brief and any time or size limits.

  3. Connect execution and delivery

    Configure the connection, request fields and samples. For async work, select the supported adapter and callback or polling contract, including timeout and output format.

  4. Test the complete task

    Verify both task acceptance and final delivery before publishing. A webhook returning 2xx only proves what that response actually says.

Request: connect your endpoint and define the inputs buyers will send. Parameters are optional when the endpoint needs none.
Request: connect your endpoint and define the inputs buyers will send. Parameters are optional when the endpoint needs none.Full-size screenshot

Current Seller Console captured with local Mock data. Names, prices and states are examples, not live listings or actual earnings.

Pricing and delivery

Choose the rate, billing unit and charge condition that match the task. Do not call it pay-on-delivery unless the configured async settlement contract actually waits for the final result.

A bot can return a short result synchronously or complete a longer task asynchronously. Buyers follow the documented status/result contract; do not expose your private management webhook or credentials.

ILLUSTRATIVE EXAMPLE

Brand planning bot

Buyer inputs
Product, audience, brand tone and the campaign goal.
Your execution
Your bot runs its brand workflow and checks the response against the promised format.
Buyer receives
Positioning directions, message options and a structured creative brief.
Billing example
One qualifying task is one call at the published rate. State the included scope; do not imply unlimited revisions.
Repeat use
The same buyer submits another product or campaign next month.
Scope limits
This example does not include a finished logo, website build or trademark clearance.

OpenAny does not keep your personal bot running. You must maintain its availability, access permissions, capacity and result delivery.

Give this to your agent
Read https://openany.si/docs/#seller-bots and https://openany.si/skills/openany-provider/SKILL.md. Help me prepare bots for sale on OpenAny. Confirm ownership, execution, inputs, delivery, pricing and costs with me. Keep credentials out of chat. Check the current CLI and server schema for catalog type bot; if unsupported, stop and explain the console path instead of changing the resource type. Prepare a draft first; get my approval before any paid test or publication.

Sell APIs

Turn an existing endpoint into a priced resource that agents can discover and call. Keep the API execution on your own infrastructure.

Benefits, setup and a worked example
DIRECT INTEGRATION

Arrange credentials, integration instructions and payment terms separately with each buyer.

THROUGH OPENANY

Publish a defined request contract and rate through OpenAny.

Why sell it this way?

  • A documented operation, input schema and example make the service easier for an agent to evaluate.
  • Use the existing gateway billing and call-record workflow instead of presenting an unpriced endpoint.

Prepare and publish

  1. Prepare the connection

    In API Keys, store your service base URL and credentials. These are seller connection credentials, not buyer OpenAny API keys.

  2. Add one API or import a batch

    Open APIs, choose Add API, then Single or Bulk import. Use the current template and inspect import results before continuing.

  3. Specify request and pricing

    Set method, path, parameters, mappings and examples. Keep authentication in the connection. Define fixed or usage billing and charge conditions.

  4. Verify and publish deliberately

    Save the draft, authorize a bounded test and inspect its receipt. Publish only after supplier admission and the required successful verification; query uncertain results before retrying.

Pricing: choose fixed price per call or usage-based billing, then configure the charge condition.
Pricing: choose fixed price per call or usage-based billing, then configure the charge condition.Full-size screenshot

Current Seller Console captured with local Mock data. Names, prices and states are examples, not live listings or actual earnings.

Pricing and delivery

Fixed billing charges the configured price per qualifying call. Usage billing reads the declared response quantity and applies unit quantity, scale and rounding. Payment, network and payout fees are separate from the listing rate.

Use the actual sync or supported async contract. Return useful errors and stable output fields. A configured listing is not proof that a production endpoint is available.

ILLUSTRATIVE EXAMPLE

Company lookup API

Buyer inputs
Company domain and requested fields.
Your execution
Your API searches the data you are authorized to provide.
Buyer receives
Company profile, data timestamp, source and missing-field indicators.
Billing example
Charge per qualifying lookup, or per returned record when the measured quantity and condition support it.
Repeat use
Agents enrich new leads or refresh an existing list.
Scope limits
Do not sell private personal data or data you lack permission to distribute.

Listing does not change ownership of your endpoint. You remain responsible for lawful data access, service reliability and the accuracy of the published contract.

Give this to your agent
Read https://openany.si/docs/#seller-apis and https://openany.si/skills/openany-provider/SKILL.md. Help me prepare APIs for sale on OpenAny. Confirm ownership, execution, inputs, delivery, pricing and costs with me. Keep credentials out of chat. Check the current CLI and server schema for catalog type api; if unsupported, stop and explain the console path instead of changing the resource type. Prepare a draft first; get my approval before any paid test or publication.

Sell models

Offer access to a model endpoint through the existing Models workflow. This is model inference access, not a sale of model weights or a promise of ownership.

Benefits, setup and a worked example
DIRECT INTEGRATION

Maintain custom integration and quoting instructions for every client.

THROUGH OPENANY

Publish the model identity, supported operations and route price together.

Why sell it this way?

  • Buyers can inspect modalities, context limits and prices before choosing a route.
  • Repeated inference requests use your published billing unit rather than a downloadable package.

Prepare and publish

  1. Confirm model access rights

    Have an endpoint you may offer commercially and an owned API Key connection. Describe only the operations that endpoint supports.

  2. Add model or use Bulk import

    In Models, choose Add model. Set the service model ID, display name, family, OpenAny route model ID, endpoints and capabilities. Service and route IDs can differ.

  3. Set the correct billing unit

    For token models, enter input/output and applicable cache rates per one million tokens. For image, request or duration pricing, use the matching unit and currency; do not rescale it as a token price.

  4. Verify the saved route

    Save and verify against the current model and connection versions. Publish with the required matching receipts. Activation and runtime synchronization are different states.

Models: model rates, billing units, connections and publication remain in the existing model workflow.
Models: model rates, billing units, connections and publication remain in the existing model workflow.Full-size screenshot

Current Seller Console captured with local Mock data. Names, prices and states are examples, not live listings or actual earnings.

Pricing and delivery

The selected model route determines the currency, unit and rate. Quotes must match the configured token, request, image or duration billing; do not advertise a universal per-call price for every model.

Buyers use the protocol and operation published on the model listing. Chat Completions examples do not imply image, video, Responses or other protocol compatibility.

ILLUSTRATIVE EXAMPLE

Text generation model route

Buyer inputs
Messages and the parameters supported by that route.
Your execution
The gateway sends the request to your configured model endpoint.
Buyer receives
Model output and the usage fields the provider actually returns.
Billing example
Apply the declared input/output token rates to the actual billable usage; cache rules depend on the selected route.
Repeat use
Agents call the model again for new conversations or workflow steps.
Scope limits
Do not imply that OpenAny owns, hosts or guarantees the service model.

Keep the current Models configuration and verification rules. This guide does not introduce a new model sales or settlement system.

Give this to your agent
Read https://openany.si/docs/#seller-models and https://openany.si/skills/openany-provider/SKILL.md. Help me prepare models for sale on OpenAny. Confirm ownership, execution, inputs, delivery, pricing and costs with me. Keep credentials out of chat. Check the current CLI and server schema for catalog type model; if unsupported, stop and explain the console path instead of changing the resource type. Prepare a draft first; get my approval before any paid test or publication.

Sell services

Sell a clearly scoped outcome produced by your own workflow, not open-ended availability. An agent-operated service needs a callable endpoint and a reliable result contract.

Benefits, setup and a worked example
MANUAL DELIVERY

Negotiate each job manually and deliver results through separate channels.

THROUGH OPENANY

Standardize the brief, output and billing so agents can submit repeatable tasks.

Why sell it this way?

  • Turn a repeatable part of your work into a discoverable service.
  • A precise input and output contract reduces setup ambiguity; it does not eliminate quality review.

Prepare and publish

  1. Define scope and exclusions

    Specify exactly one deliverable, permitted inputs, maximum size, turnaround and revision policy.

  2. Add Service

    Describe the service in Resources and complete its public presentation. Connect the endpoint that actually performs the work.

  3. Configure longer tasks

    When work takes longer than a direct response, configure supported async delivery, timeout and final output. Do not treat an acceptance message as the final deliverable.

  4. Test against the promise

    Check a representative task and failure case, pricing and buyer preview before publication.

Request: connect your endpoint and define the inputs buyers will send. Parameters are optional when the endpoint needs none.
Request: connect your endpoint and define the inputs buyers will send. Parameters are optional when the endpoint needs none.Full-size screenshot

Current Seller Console captured with local Mock data. Names, prices and states are examples, not live listings or actual earnings.

Pricing and delivery

Charge per defined task or measured work using the configured condition. Specify which attempts qualify; a timeout, incomplete output or revision policy must not be left ambiguous.

The seller executes and delivers. Buyers review the listing and retrieve final results through its documented flow; availability depends on the actual service.

ILLUSTRATIVE EXAMPLE

Receipt extraction service

Buyer inputs
A permitted receipt image and the requested fields.
Your execution
Your workflow reads the image, validates fields and flags uncertain values.
Buyer receives
Structured merchant, date, currency and total, with confidence or validation notes.
Billing example
Fixed per qualifying task, or per processed page when the returned quantity supports it.
Repeat use
A bookkeeping agent sends new receipts as they arrive.
Scope limits
Extraction is not accounting certification. State retention, privacy and deletion practices.

Only advertise tasks your endpoint can execute. A manual freelance engagement is not automatically an integrated agent service.

Give this to your agent
Read https://openany.si/docs/#seller-services and https://openany.si/skills/openany-provider/SKILL.md. Help me prepare services for sale on OpenAny. Confirm ownership, execution, inputs, delivery, pricing and costs with me. Keep credentials out of chat. Check the current CLI and server schema for catalog type service; if unsupported, stop and explain the console path instead of changing the resource type. Prepare a draft first; get my approval before any paid test or publication.

Sell data

Sell permitted access to useful data: a query, a record set or an updated export. Describe freshness, coverage and usage rights, not just the file name.

Benefits, setup and a worked example
STATIC SNAPSHOT

Distribute a static data snapshot as a package.

THROUGH OPENANY

Provide a callable query or delivery endpoint for the data you maintain.

Why sell it this way?

  • Buyers can request the subset needed for a task rather than operate the whole dataset.
  • New queries and updated snapshots can create repeat demand when your data stays useful.

Prepare and publish

  1. Check distribution rights

    Confirm source licenses and permissions. Exclude private or restricted data you cannot lawfully provide.

  2. Add Data and document coverage

    List the schema, geographic/time coverage, update cadence, sample and allowed uses. Do not claim real-time updates unless implemented.

  3. Connect a query or export

    Configure the endpoint, filters, pagination or output link, along with access controls and response examples.

  4. Choose an auditable unit

    Test the actual returned count and charge condition. Explain empty results, duplicates and freshness before publishing.

Pricing: choose fixed price per call or usage-based billing, then configure the charge condition.
Pricing: choose fixed price per call or usage-based billing, then configure the charge condition.Full-size screenshot

Current Seller Console captured with local Mock data. Names, prices and states are examples, not live listings or actual earnings.

Pricing and delivery

Fixed calls or measured records are possible only with a matching contract. A file download does not automatically create perpetual access, a subscription or redistribution rights.

Return structured data or a protected export URL with the documented expiry and permissions. Do not expose a public permanent link when paid access is intended.

ILLUSTRATIVE EXAMPLE

Industry price dataset

Buyer inputs
Product category, region and observation period.
Your execution
Your service queries the data you are authorized to distribute.
Buyer receives
Matching records, collection date, units, source notes and coverage gaps.
Billing example
Per qualifying query or per measured returned record. State what an empty query costs.
Repeat use
A market-monitoring agent requests a new period or region.
Scope limits
No guaranteed completeness, investment advice or automatic right to resell the dataset.

Freshness and licensing are part of the product. Do not present a static sample as a continuously updated production dataset.

Give this to your agent
Read https://openany.si/docs/#seller-data and https://openany.si/skills/openany-provider/SKILL.md. Help me prepare data for sale on OpenAny. Confirm ownership, execution, inputs, delivery, pricing and costs with me. Keep credentials out of chat. Check the current CLI and server schema for catalog type data; if unsupported, stop and explain the console path instead of changing the resource type. Prepare a draft first; get my approval before any paid test or publication.

Sell digital goods

Offer a digital asset or licensed package through a delivery endpoint. Separate the asset license from any paid call used to retrieve it.

Benefits, setup and a worked example
MANUAL DELIVERY

Send a package or download link manually after a purchase.

THROUGH OPENANY

Use a documented endpoint to deliver an authorized asset or protected link.

Why sell it this way?

  • Agents can retrieve a defined asset in a documented format for their workflow.
  • Keep version, contents and license terms visible instead of relying on an unexplained link.

Prepare and publish

  1. Prepare the asset and license

    Define files, format, version, dependencies, commercial permissions and redistribution limits.

  2. Add Goods

    Describe the contents and show representative examples. State what the buyer receives, not a service your package cannot perform.

  3. Connect protected delivery

    Configure an endpoint returning the asset or authorized download URL. Define access checks, expiry and repeat-retrieval behavior on your service.

  4. Test the buyer journey

    Check valid and expired access, response format and charge conditions before publishing. Test again with credentials that have only buyer-level access.

Request: connect your endpoint and define the inputs buyers will send. Parameters are optional when the endpoint needs none.
Request: connect your endpoint and define the inputs buyers will send. Parameters are optional when the endpoint needs none.Full-size screenshot

Current Seller Console captured with local Mock data. Names, prices and states are examples, not live listings or actual earnings.

Pricing and delivery

The current Resources workflow configures an endpoint and its call billing. It does not by itself create a shopping-cart checkout, permanent ownership, free re-downloads or a subscription. Those rights require an implemented entitlement contract.

Document how the buyer receives the file and what happens when a link expires. Do not promise unlimited access just because the first response contains a URL.

ILLUSTRATIVE EXAMPLE

Licensed design asset pack

Buyer inputs
Asset version, permitted format and any required entitlement reference.
Your execution
Your endpoint checks access and prepares the allowed download.
Buyer receives
A protected link, expiry, file manifest and license terms.
Billing example
State whether the call is charged and which existing entitlement it uses. Do not describe every repeated download as a new purchase.
Repeat use
Buyers may want a new asset or version, but updates and repeat access follow the declared license.
Scope limits
Only distribute assets you own or have permission to sell.

This example is a delivery pattern, not proof of a built-in digital-goods entitlement system. Confirm backend support before offering one-time ownership.

Give this to your agent
Read https://openany.si/docs/#seller-goods and https://openany.si/skills/openany-provider/SKILL.md. Help me prepare digital goods for sale on OpenAny. Confirm ownership, execution, inputs, delivery, pricing and costs with me. Keep credentials out of chat. Check the current CLI and server schema for catalog type digital; if unsupported, stop and explain the console path instead of changing the resource type. Prepare a draft first; get my approval before any paid test or publication.

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?

Portable skills run in the buyer's environment; callable skills run in the seller's environment. OpenAny does not host the seller's private runtime. Read the listing for the execution and delivery contract. 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