apiosk

The problem

Integrating diverse third-party APIs requires managing multiple API keys, subscriptions, and payment methods. AI agents often lack a safe way to authorize individual paid transactions without exposing full credit card access or handling complex crypto signing.

What it does

• Discovers and searches for available paid APIs across categories like weather, finance, and logistics.
• Performs free preflight checks to validate request parameters before incurring costs.
• Executes paid API calls using a single connect token for unified authentication.
• Handles automated settlement via USDC on Base or SEPA prepaid ledgers.
• Ensures transaction safety through mandatory idempotency keys to prevent double-charging.

Frameworks & tools

Compatible with any HTTP client or MCP-compliant environment like Claude Code or Cursor. Uses USDC (x402 on Base) and SEPA for payments.

Why this beats prompting it yourself

This skill implements the full API discovery and payment lifecycle correctly, including receipt logging and idempotency logic. Without it, agents struggle to navigate the "pay-per-call" handshake and often fail to handle network timeouts without risking multiple charges.

Use cases

• Generating shipping labels or SMS alerts without managing per-service accounts.
• Accessing premium financial or weather data on a per-query basis.
• Building automated agents that scale costs linearly with usage rather than fixed monthly fees.

Known limitations

The agent cannot choose the payment rail; the gateway automatically selects between USDC and SEPA. Requires a pre-configured budget via a connect token.