FLUSHNET DEVELOPER PLATFORM

API endpoints and API keys in one place.

Customer applications authenticate with account-scoped Flushnet API keys. Internal execution details remain private.

PUBLIC BASE URLS Flushnet AI APIhttps://api.flushnet.net/v1 Flushnet MCPhttps://mcp.flushnet.net/mcp Canonical public names. Routes marked Reserved below must not be treated as live until gateway activation is completed.

AUTHENTICATION

Your API keys

Keys are account-bound. Secret values are shown once when created; stored records expose only a prefix and usage metadata.

Name	Prefix	Created	Last used	Status
Loading…

ai:chatai:modelsai:imageai:audioai:videomcp:toolsmcp:resourcesagents:execute

The current Compute key service is live. Unified per-key scopes for the public AI/MCP gateway are the target model and are not presented as active until that gateway binding is enabled.

FLUSHNET AI API

OpenAI-compatible AI surface

One stable public AI interface for supported AI operations.

POST/v1/responsesReserved

POST/v1/chat/completionsReserved

GET/v1/modelsReserved

GET/v1/usageReserved

POST/v1/images/generationsReserved

POST/v1/audio/transcriptionsReserved

POST/v1/audio/speechReserved

POST/v1/videosReserved

FLUSHNET MCP

MCP access

The same customer identity and future unified Flushnet key can authorize MCP tools and resources.

POSThttps://mcp.flushnet.net/mcpReserved

GEThttps://mcp.flushnet.net/mcpReserved

COMPUTE API

Current account API

These endpoints already use the live Flushnet Compute account/key system.

GET/POST/flushnet-compute/api/index.php?action=<action>Live

AUTH FORMAT

One customer credential format

Authorization: Bearer <FLUSHNET_API_KEY>

Where supported, X-API-Key: <FLUSHNET_API_KEY> can be used as a compatibility transport.

Example target request

POST https://api.flushnet.net/v1/chat/completions
Authorization: Bearer <FLUSHNET_API_KEY>
Content-Type: application/json

{
  "model": "flushnet-ai",
  "messages": [
    {"role":"user","content":"Hello from my app"}
  ]
}