API access for agent clients

Use your Writingmate plan in the agent tools you already run.

Connect OpenAI-compatible coding agents, SDKs, automation tools, and MCP hosts to Writingmate with one Developer Key. Keep your Writingmate workspace, model access, and plan accounting.

Create Developer KeyView integration docs
OpenAI-compatible /v1 API
MCP JSON-RPC endpoint
Same plan and workspace limits
writingmate provider

Base URL

https://writingmate.ai/api/openai/v1
{
  "provider": "writingmate",
  "api": "openai-compatible",
  "baseURL": "https://writingmate.ai/api/openai/v1",
  "model": "google/gemini-2.5-flash"
}
OpenAI-compatible Writingmate configuration example

Create a Developer Key

Generate a Writingmate Developer Key from the API Keys tab in your account settings.

Point your client at Writingmate

Use https://writingmate.ai/api/openai/v1 as the OpenAI-compatible base URL.

Pick a Writingmate model slug

Call /models or choose a documented slug such as google/gemini-2.5-flash.

Use MCP when the client supports tools

Connect MCP hosts to https://writingmate.ai/api/mcp for JSON-RPC tool discovery.

Client ecosystem

Bring Writingmate into standards-compatible clients.

The API is built for agent users who want model choice without rebuilding their local workflow. Use direct OpenAI-compatible calls first, then MCP where the host supports tool discovery.

ClientSurfaceStatus

OpenAI SDKs

Set baseURL and apiKey

OpenAI-compatible APIStandards-compatible

Vercel AI SDK

Use @ai-sdk/openai-compatible

OpenAI-compatible APIDocumented config

Continue

Set provider, apiBase, apiKey, model

OpenAI-compatible APIDocumented config

Aider

Set OPENAI_API_BASE and model

OpenAI-compatible APIDocumented config

OpenCode / OpenClaw-style clients

Add Writingmate as a custom provider

OpenAI-compatible APIConfigurable

MCP hosts

Connect https://writingmate.ai/api/mcp

MCPStandards endpoint

OpenAI-compatible API

Use /models, /chat/completions, /responses, image, and video endpoints from SDKs and agent clients.

Read docs

MCP endpoint

Connect MCP-capable hosts to Writingmate tools for model listing and generation calls.

Read docs

Plan-aware access

Requests count against the same Writingmate workspace plan and model access rules as the app.

Read docs

Setup values for every client.

Most agent clients only need a base URL, a Bearer token, and a model name. Use MCP when the host expects a standards-based tool server.

OpenAI base URLhttps://writingmate.ai/api/openai/v1
MCP endpointhttps://writingmate.ai/api/mcp
Auth headerAuthorization: Bearer YOUR_WRITINGMATE_DEVELOPER_KEY
Workspace headerx-writingmate-workspace: WORKSPACE_ID

FAQ

What is the Writingmate API for agent clients?

The Writingmate API lets agent clients use Writingmate models through an OpenAI-compatible API and an MCP endpoint. Users authenticate with a Writingmate Developer Key and keep the same plan limits they already use in the web app.

Can I use my existing Writingmate plan through the API?

Yes. Developer Key requests use the authenticated Writingmate workspace, plan access, daily message counting, and configured BYOK provider keys where supported.

Which clients can connect to Writingmate?

Any client that supports a custom OpenAI-compatible base URL and Bearer token can target Writingmate. MCP hosts can connect through the Writingmate MCP endpoint for model and generation tools.

Does Writingmate replace Codex or Claude Code?

No. Writingmate exposes model access into existing agent ecosystems. Codex-style and Claude-style clients remain the local tools; Writingmate provides the API and model plan behind them where those clients support custom providers.