---
name: zipflow
description: Operate the ZipFlow model API service as an AI agent. Use when you need to use ZipFlow to call a model (OpenAI, Anthropic, rerank, or realtime), set the correct base URL per protocol, list current models and prices, check platform status, or make an agent-funded payment when you have no wallet or balance.
version: 1.0.0
---

# ZipFlow — Platform Agent Skill

You are operating ZipFlow (a hosted model API service) on behalf of the user. One API key covers every supported protocol; your job is to pick the right base URL and make the call.

## How to use ZipFlow

### A. The user has a ZipFlow API key (common path)

1. Ask the user for their ZipFlow API key (sk-...). If they do not have one, point them to https://zipflow.xyz/en/register to create an account and issue a key in the console.
2. Set the base URL for the protocol you are calling (table below).
3. Call the endpoint with Authorization: Bearer <api key>.

### B. You have no wallet or balance (agent-funded path)

If the user wants you to pay for usage and you have no wallet or funds, follow the x402 agent-payment protocol instead of a user-supplied key. Read its full, authoritative instructions first: https://api.zipflow.xyz/x402/skill.txt . It covers self-registering an Ed25519 identity, minting a short-lived JWT credential and an LLM token, and raising a payment for a human to settle when you run out of balance.

## Base URLs per protocol

A trailing /v1 is required for OpenAI-compatible clients and must be omitted for Anthropic-compatible clients.

- **OpenAI-compatible** — base https://api.zipflow.xyz/v1 (OPENAI_BASE_URL). Endpoints: POST /v1/chat/completions, POST /v1/responses, POST /v1/embeddings, GET /v1/models.
- **Anthropic-compatible** — base https://api.zipflow.xyz (ANTHROPIC_BASE_URL, no trailing /v1). Endpoint: POST /v1/messages.
- **Rerank** — POST https://api.zipflow.xyz/v1/rerank (Cohere, Jina AI, and Xinference formats).
- **Realtime** — POST https://api.zipflow.xyz/v1/realtime/sessions (WebRTC and WebSocket).

## Current models and prices

- GET https://api.zipflow.xyz/v1/models — models available to your key.
- https://zipflow.xyz/en/pricing — per-1M-token USD prices for every model.

## Platform status

- https://status.zipflow.xyz/status.json — live platform status, uptime, online models, and validation results (JSON).
- https://status.zipflow.xyz/skill.txt — the status site's own agent skill for querying status and model purity.

## Documentation

- https://docs.zipflow.xyz/en — API reference for the formats above and app integration guides.

## Keeping this skill current

1. Re-fetch this file before answering: https://zipflow.xyz/skill.txt is server-rendered fresh on every request (Cache-Control max-age=60), so a re-fetch always returns the current definition.
2. Compare the frontmatter version with any cached copy. If your copy has an older version than the one served now, discard it and use the new one.
3. The response header X-Skill-Version mirrors the frontmatter version, so an HTTP-level check can detect definition changes without parsing the body.
4. Product-level changes are logged on the main site changelog: https://zipflow.xyz/en/changelog (RSS: https://zipflow.xyz/changelog.xml).

## Related agent surfaces

- MCP server: https://mcp.zipflow.xyz — initialize returns serverInfo.version; call tools/list to refresh the tool definitions.
- x402 agent payments: https://api.zipflow.xyz/x402/skill.txt.
- Status skill: https://status.zipflow.xyz/skill.txt.