OpenAI-compatible Access

Your pod exposes an OpenAI-compatible endpoint, so you can drive the agent from any OpenAI client, SDK, framework (LangChain, LlamaIndex, etc.), or router — no bespoke integration. Each request runs one agent turn, with the same model, wallet, autonomy, and spend policies as the dashboard Chat.

This is a beta feature and only appears once it’s enabled for the platform. You’ll find it in the pod workspace under Settings → OpenAI-compatible access.

1. Create a key

In the pod’s Settings → OpenAI-compatible access:

Copy the base URL — it looks like https://compute.x402layer.cc/pods/{id}/v1.
Give a key a name (e.g. “my app”) and hit Create key. The key is shown once — copy it immediately.

You can create multiple keys and revoke any of them instantly if one leaks. Each key shows when it was last used and its per-day request count.

Anyone with a key can instruct this agent within its current autonomy and wallet settings. Treat keys like secrets, and revoke immediately if one is exposed. See Wallet for spend caps.

2. Point any OpenAI client at it

Use the base URL as baseURL and your pod key as the API key.

from openai import OpenAI

client = OpenAI(
    base_url="https://compute.x402layer.cc/pods/{id}/v1",  # from Settings
    api_key="<your-pod-key>",                              # created above
)

resp = client.chat.completions.create(
    model="agent-pod",  # the pod runs its own configured model
    messages=[{"role": "user", "content": "What's on my schedule today?"}],
)
print(resp.choices[0].message.content)

# Discover the model
curl https://compute.x402layer.cc/pods/{id}/v1/models \
  -H "Authorization: Bearer <your-pod-key>"

# Run one agent turn
curl https://compute.x402layer.cc/pods/{id}/v1/chat/completions \
  -H "Authorization: Bearer <your-pod-key>" \
  -H "Content-Type: application/json" \
  -d '{"model":"agent-pod","messages":[{"role":"user","content":"hi"}]}'

What to expect

One turn per request — a call runs the agent once (it may use its tools, wallet, skills, and memory), then returns the reply. It’s the agent answering, not a raw model passthrough.
The pod’s model — the request uses whatever model the pod is set to (Settings → Model applies across chat, Telegram, and this API). See Models.
Same policies as chat — the pod’s wallet, autonomy mode, and spend caps all apply to API-driven turns.

The pod’s configured model is the source of truth — you don’t select an arbitrary model per request the way you would against a raw provider. Set the model once in Settings → Model.

Full API spec

The examples above are the essentials. For the complete endpoint list, auth details, request/response schemas, and field-level reference, see the API reference.

Models

Set the model this API uses.

Wallet

Spend caps that apply to API turns.

API reference

The full spec.

Overview

User Guide

Slayer Agent

Core flows

Staking Engine

Singularity Cloud Network

Contract Addresses

ERC8004

Skills

Singularity Payments

Agentic Fundraisers

Enterprise

1. Create a key

2. Point any OpenAI client at it

What to expect

Full API spec

Models

Wallet

API reference

​1. Create a key

​2. Point any OpenAI client at it

​What to expect

​Full API spec

​Related

Models

Wallet

API reference

1. Create a key

2. Point any OpenAI client at it

What to expect

Full API spec

Related