# BeefAPI Global Use https://global.beefapi.com/v1 with an API key created on https://global.beefapi.com. Anthropic clients use the host root. Global keys spend prepaid USD credit; domestic keys and wallets are separate. ## Sources - Documentation: https://global.beefapi.com/docs - Current USD prices: https://global.beefapi.com/pricing.usd.json - Human price table: https://global.beefapi.com/pricing - API schema: https://global.beefapi.com/openapi.json - Full documentation: https://global.beefapi.com/llms-full.txt - API reference: https://global.beefapi.com/docs/api — Call models with an API key, and read account credit with a separate system access token. - Billing: https://global.beefapi.com/docs/billing — Understand USD credit, token and media charges, reserved credit, failed tasks, and usage records. - Clients: https://global.beefapi.com/docs/clients — Point an OpenAI-compatible or Anthropic-compatible client at BeefAPI with a Base URL and an API key. - Errors: https://global.beefapi.com/docs/errors — How to read BeefAPI HTTP errors and what to do when a request fails. - Images: https://global.beefapi.com/docs/images — Generate and edit images with gpt-image-2, save the result, and handle long requests. - Models: https://global.beefapi.com/docs/models — Match model IDs to text, image, and video endpoints and check current availability and USD prices. - Quickstart: https://global.beefapi.com/docs/quickstart — Create a global API key, add USD credit, send your first request, and read the result. - Videos: https://global.beefapi.com/docs/videos — Generate videos from text or images, poll the task, and download the completed MP4. ## Request shapes Text uses Chat Completions, Responses, or Anthropic Messages. Images use /v1/images/generations or /v1/images/edits. Videos use POST /v1/videos, GET /v1/videos/{id}, then GET /v1/videos/{id}/content. A queued task is not a finished asset. Image jobs are optional and route-dependent. Global video editing is not offered. Model listings do not guarantee immediate capacity. Use the USD pricebook, then check authenticated usage for final charges. The shared /pricing.json is a different catalog; do not use its currency conversion as global USD pricing.