For AI builders | UnitAPI

Use UnitAPI as a tool layer for general-purpose AI agents

OpenAPI JSON

llms.txt

UnitAPI exposes stateful backend primitives that LLMs and agent runtimes can call for tasks, subscriptions, short links, and more. The integration surface is designed around OpenAPI, predictable JSON payloads, and API-key auth.

OpenAPI-firstX-API-Key authStatic llms.txtAgent-friendly JSON

Start with the machine-readable references

Discoverability

Use the public OpenAPI document for tool schemas and llms.txt for a compact summary of what UnitAPI offers to agents.

• OpenAPI JSON: https://api.unitapi.cloud/api-docs-json
• Human docs: https://api.unitapi.cloud/api-docs
• llms.txt: /llms.txt

MCP server availability

MCP

The UnitAPI MCP server is not published yet.

Coming soon

Plan today around OpenAPI plus API keys. When the MCP endpoint is public, this page will link the server URL and supported tools.

OpenAI function-calling JSON

{
  "type": "function",
  "function": {
    "name": "create_task",
    "description": "Create a task in UnitAPI",
    "parameters": {
      "type": "object",
      "properties": {
        "title": { "type": "string" },
        "status": { "type": "string", "enum": ["todo", "in_progress", "done"] }
      },
      "required": ["title"]
    }
  }
}

Anthropic tool schema JSON

{
  "name": "create_short_link",
  "description": "Create a short redirect in UnitAPI",
  "input_schema": {
    "type": "object",
    "properties": {
      "slug": { "type": "string" },
      "url": { "type": "string", "format": "uri" }
    },
    "required": ["slug", "url"]
  }
}

Raw curl examples

curl -X GET 'https://api.unitapi.cloud/api-docs-json' \
  -H 'Accept: application/json'

curl -X POST 'https://api.unitapi.cloud/tasks' \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: $UNITAPI_API_KEY' \
  -d '{"title":"Summarize inbound leads","status":"todo"}'

Use X-API-Key for agent traffic

Authentication

Provision keys in the UnitAPI console, store them in your model runtime, and send them as X-API-Key for server-to-server calls.

• API keys are the default choice for tool use and background jobs.
• Session cookies still work for browser operators using the console.
• Keep scopes narrow when you create keys for a single workflow.

Plan for quotas and rate limits

Limits

Monthly quotas come from the active pricing plan, while service-level rate limits protect shared infrastructure.

• Expect request quotas to align with your chosen plan tier.
• Burst capacity can be raised for production automations.
• Monitor usage in the console before long-running autonomous jobs scale up.