https://mcp.agentmuxer.com/mcp. Personal clients sign in through their supported authentication flow. Applications send their API key as a bearer token. Authentication is required for free discovery as well as paid calls.
The SDK helpers configure this connection for your framework. The examples below are MCP tool arguments, not methods exported by the SDK.
search_offerings
Find available capabilities. Searching does not invoke a provider or spend credits.string
Optional search text, up to 500 characters. Omit it to browse.
integer
Optional page size from 1 to 50.
string
An opaque cursor returned by an earlier search. Keep the same filters when paging.
"after" | "before"
default:"after"
Page forward or backward with a cursor.
Additional filters
Additional filters
Use arrays for
publisherIds, protocols, taskFamilies, tags, trustTiers, capabilityGroups, and useCases. Use values from the catalog. Trust tiers are indexed, verified, and benchmarked; they describe available evidence, not a guarantee of useful output.items, with each item’s offeringVersion.id, description, availability, and price when priced. Use the returned nextCursor or prevCursor to continue.
inspect_offering
Inspect the exact version selected from search before calling it.UUID string
required
The
offeringVersion.id returned by search.call_offering
Execute the inspected capability. Supply a new idempotency key for each new logical purchase.UUID string
required
The exact version you inspected.
decimal string
required
Maximum initially authorized charge in USD credit micros, encoded as a non-negative whole-number string without a decimal point or leading zeros. One dollar is
"1000000"; ten cents is "100000". Use "0" to authorize no positive charge unless revised terms are explicitly accepted.string
required
A non-empty identifier up to 200 characters. Reuse it for retries of the same purchase.
object
required
Provider inputs using the inspected interface. Use
{} when the tool requires no inputs.UUID string
Optional acceptance reference returned with revised price terms. Do not invent this value.
Example arguments
Replace the example version ID with one returned by search, and supply the inputs required by that tool’s inspected interface.Request inputs
Do not pass your AgentMuxer application key as a tool input. Authentication belongs on the MCP connection.
Purchases and retries
1
Use the price and interface you inspected
Submit the exact offering version, inputs, maximum charge, and an idempotency key. Account balance, application caps, and payment confirmation still apply.
2
Handle revised terms explicitly
If the response has
status: "price_confirmation_required", review the exact cost and expiry. To accept, repeat the original call unchanged, including its maximum and key, adding the returned continuation.acceptTerms. If you decline, stop. Acceptance does not override spending limits.3
Preserve the purchase identity
A replay with the same key returns the existing result without another execution or charge. A client timeout is not evidence that no purchase happened. Check the existing call rather than starting another purchase. Expired confirmation terms require a new key after you decide to start a new purchase.
Results
object
The invocation result, including the provider response and invocation identifier.
decimal string
The tool cost in USD credit micros.
"finalized" | "pending"
Whether accounting has finalized. A pending charge is not a reason to buy the tool again.
boolean
Whether this is a replay of an existing purchase.
decimal string
Account balance when present in the response.
refusedBy and relevant recovery information. An insufficient-balance response can include a topupUrl; show it to the account owner. Follow troubleshooting instead of blindly retrying.
report_outcome
Report whether an invocation helped with the task. This feedback is separate from the provider’s HTTP response and billing.UUID string
required
The invocation identifier returned by the call.
"succeeded" | "failed" | "not-useful"
required
Choose the result that describes the task outcome.
string
Optional explanation up to 1,000 characters. Do not include secrets.
accepted and duplicate. Repeated reports from the same account for an invocation are acknowledged without recording another report.
Billing, limits, and approvals
See when charges apply and how framework permissions differ from payment confirmation.