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

# Overview

> One API for free, x402, prepaid, and durable multimodal inference

The Pearl Inference API exposes multiple providers behind one model
catalog and one chat endpoint. Model ids are namespaced as
`provider/upstream-model-id`; unprefixed ids remain Dolphin for backward
compatibility.

## Base URL

```
https://pearl.computer/v1
```

## Endpoints

<CardGroup cols={2}>
  <Card title="Chat Completion" icon="message" href="/api-reference/inference/chat">
    `POST /v1/inference/chat` — unified SSE chat
  </Card>

  <Card title="List Models" icon="microchip" href="/api-reference/inference/models">
    `GET /v1/inference/models` — merged catalog
  </Card>

  <Card title="Providers" icon="server" href="/api-reference/inference/providers">
    `GET /v1/inference/providers` — capabilities and settlement
  </Card>

  <Card title="Media" icon="image" href="/api-reference/inference/media">
    Durable images, video, music, jobs, and library
  </Card>

  <Card title="List Templates" icon="list" href="/api-reference/inference/templates">
    Dolphin-only templates
  </Card>
</CardGroup>

## Payment kinds

* `none`: call immediately; Dolphin is the current free provider.
* `x402`: call once for a validated `402` offer, sign it, and retry with
  `PAYMENT-SIGNATURE`.
* `prepaid`: fund the provider balance using its registry `topup` block.
* `platform`: Pearl collects a fixed configured charge and pays the async
  upstream using a platform credential; failed/canceled jobs are refunded.

Payment values are additive. Clients should skip unknown values.

## Durable media

Generated artifacts are captured into Pearl object storage before success
is reported. Returned `url` values are durable public capability URLs suitable
for agent memory, later downloads, or chaining into another media request.
Library listing and deletion require a short-lived signature from the derived
buyer key.

<Note>
  Always fetch the current model/provider catalogs. Provider availability,
  pricing, modality, and payment mechanics are registry data rather than client
  constants.
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.