> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apiosk.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Fastest path to discover an API, handle payment, and execute a request through the gateway.

# Quickstart

If you want to wire Apiosk directly into Claude Code or Codex as an MCP server, start with [Claude Code and Codex](/guides/mcp-clients). In local stdio mode, the recommended first step is `apiosk_get_started`, which can save a dashboard connect string or create a local wallet and then immediately run a test call.

## 1. Find a listing

```bash theme={null}
curl "https://gateway.apiosk.com/v1/apis?search=vision&limit=5"
```

## 2. Read the metadata

```bash theme={null}
curl https://gateway.apiosk.com/vision-flux-v4/metadata
```

Use this response to identify:

* the default operation
* input and output shape
* price and latency hints
* tags and MCP-style tool metadata

## 3. Execute the API

Default-operation APIs accept raw JSON:

```bash theme={null}
curl -X POST https://gateway.apiosk.com/vision-flux-v4/execute \
  -H "Content-Type: application/json" \
  -H "x-payment: <proof>" \
  -d '{
    "image_url": "https://example.com/photo.jpg",
    "prompt": "Detect the main objects in this image"
  }'
```

## 4. Handle the 402 challenge

If payment is required and no valid proof is attached, the gateway returns `HTTP 402 Payment Required`.

At that point you can either:

* attach a raw `x-payment` proof from your own payer flow
* use a dashboard-managed wallet or connect string flow

The `402` may offer more than one settlement network (Base and Solana are live), pick any listed entry; the price is the same on all of them. See [Multi-chain Settlement](/guides/multichain).

For local MCP installs, prefer `apiosk_get_started` over manually managing the first paid call. It will set up the local wallet or saved connect-token state and tell you whether the next step is `ready`, `needs_funding`, or more specific input.

## 5. Read the normalized result

The public agent contract returns a wrapped response:

```json theme={null}
{
  "status": "success",
  "result": {},
  "cost": 0.018,
  "latency": 1800,
  "operation": "detect",
  "api": "vision-flux-v4",
  "upstream_status": 200
}
```

## Apiosk's own APIs

Beyond third-party listings, Apiosk publishes its own first-party APIs, company and identity lookups, financial validation, web extraction, compliance checks, developer tooling, and agent trust checks. They are ordinary listings: discover and call them the same way, with `GET /v1/apis` and `POST /{slug}/execute`.