Get started with APIPay.

Head to Sign in and create your account with email or single sign-on. Your command center opens on the Overview, which is the starting point for every product: iAPI, Infinite API, API-Pay, AI Studio and Agent Swarms.

API-Pay puts any HTTPS endpoint you run behind our gateway so you can sell and govern access to it.

1. Open API-Pay in your command center and create a new API product.
2. Give it a name and a slug (for example weather). The slug becomes part of the gateway URL.
3. Enter your upstream base URL — the address of the service you already run.
4. Create one or more plans with included requests, overage pricing and a per-minute rate limit.

Each customer, partner or internal team gets its own API key tied to a plan. Create them from theKeys area of your command center.

• Keys are shown only once and stored as a secure fingerprint — copy them somewhere safe.
• Revoke a key at any time; revocation takes effect immediately at the gateway.
• Never ship keys in client-side code or public repositories.

Customers call your API through the gateway at /api/gateway/{slug}/{path}, passing their key in the x-api-key header. The gateway authenticates the key, enforces the plan's rate limit, forwards the request to your upstream and meters the call for analytics and invoicing.

curl https://YOUR_DOMAIN/api/gateway/weather/v1/forecast?city=paris \
  -H "x-api-key: YOUR_CUSTOMER_KEY"

const res = await fetch(
  "https://YOUR_DOMAIN/api/gateway/weather/v1/forecast?city=paris",
  { headers: { "x-api-key": process.env.CUSTOMER_KEY } }
);
const data = await res.json();

Requests without a valid key are rejected, and requests over the plan's rate limit receive an HTTP429 response. Usage appears in your analytics and flows into invoices automatically.

AI Studio exposes a single, OpenAI-compatible chat completions endpoint. Create an AI Studio key in your command center, then send requests to POST /api/v1/chat/completions with the header Authorization: Bearer <your AI Studio key>.

curl https://YOUR_DOMAIN/api/v1/chat/completions \
  -H "Authorization: Bearer YOUR_AI_STUDIO_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "MODEL_ID",
    "messages": [
      { "role": "user", "content": "Summarize our API usage trends in three bullets." }
    ]
  }'

import OpenAI from "openai";

const client = new OpenAI({
  baseURL: "https://YOUR_DOMAIN/api/v1",
  apiKey: process.env.AI_STUDIO_KEY,
});

const reply = await client.chat.completions.create({
  model: "MODEL_ID",
  messages: [{ role: "user", content: "Draft a launch announcement." }],
});

Choose any model available in AI Studio by setting model; the list of available models is shown in your command center. Because the endpoint is OpenAI-compatible, most existing SDKs and tools work by changing only the base URL and key.

iAPI connects a third-party API you already pay for to our API payment infrastructure. It's a one-time $5,000 per API, after which 100% of that API's recurring cost is covered.

1. Open your Overview and start iAPI onboarding.
2. Tell us which API you pay for, how you use it and your typical monthly volume.
3. Our team reviews the API for fit and confirms next steps with you.
4. Once connected, your applications keep calling the API the same way they do today.

Learn more on the iAPI page.

Infinite API delivers a custom, unlimited lifetime API as plug-in code that covers recurring API and integration costs — $2,000 one-time. Start from your Overview, describe the capability you need, and we'll scope it with you. See the Infinite API page for details.

Open Swarms, give each swarm an objective and a strategy, then switch it on. Each cycle returns ranked opportunities, estimates and suggested next steps. Swarm outputs are recommendations, not guarantees of results. Learn more on the Agent Swarms page.

• Store keys in server-side environment variables, never in browser code.
• Use one key per customer or environment so you can revoke access precisely.
• Handle 429 responses with exponential backoff.
• Review AI outputs before using them for important decisions.
• Read our Security overview and Acceptable Use Policy.