AI generation · https://api.piapi.ai
set up treg — https://treg.sciatafrica.com/llms.txt
claude mcp add --transport http treg https://treg.sciatafrica.com/mcp
Settings → Connectors → add https://treg.sciatafrica.com/mcp as a custom connector.
Add https://treg.sciatafrica.com/mcp as a remote MCP connector in its tool settings.
Settings → Connectors → Add custom connector → https://treg.sciatafrica.com/mcp.
Point it at https://treg.sciatafrica.com/mcp (HTTP transport).
curl -fsSL https://treg.sciatafrica.com/install.sh | sh
LangChain, CrewAI or any code: /call/<tool-id> + X-Treg-Token: <token>. No SDK.
Using treg, check an async video generation task. Show me the price first.
treg call piapi.task.get --query task_id=a30cb03f-a8d3-4d87-a547-c2a0d113e7a5
Connect once; treg.to keeps the credential server-side and injects it per call. No key on any machine.
The provider's own rate, $0.000 markup. How billing works.
Calls through your own connection are not metered by treg.
Register it and those calls are never metered. Your key always wins.
Another provider is a different word in the prompt, not a new integration.
The same token calls Google AI (Gemini API), OpenRouter, reAPI and 3,611 other tools.
piapi.image-gen.gemini-3-pro-imagepiapi.image-gen.gpt-image-2piapi.image-gen.gpt-image-2-5piapi.task.getpiapi.video-gen.seedance-2-5piapi.video-gen.seedance-2-5.less-restrictionReliability badges come from live traffic through treg.to. Live-verified means a successful provider check; it does not verify every request variant.
Yes. This is an own-account connection: you sign in to PiAPI once and your agent uses that connection through your treg.to token. Calls on it are never metered.
Run: claude mcp add --transport http treg https://treg.sciatafrica.com/mcp. One MCP server carries PiAPI and the rest of the catalog.
Anything that speaks MCP (Claude Code, Claude Desktop, ChatGPT, Codex, Cursor, Grok) and anything that can make an HTTP request (LangChain, CrewAI, LlamaIndex, plain code).
No. treg.to serves PiAPI's real API through its own metered proxy: the request is the provider's own, the credential is injected server-side, and the answer is relayed verbatim. The official PiAPI channels are linked above.