API for AI agents and developers

Discovery

Remote MCP endpoint: https://l2tools.org/api/mcp. It uses Streamable HTTP, requires no API key and exposes the same validated read-only operations as the REST API.

Connect an AI client

Add the following MCP tool definition to a client that accepts remote MCP servers, including the OpenAI Responses API. The endpoint is public and all tools are read-only.

{
  "type": "mcp",
  "server_label": "l2tools",
  "server_url": "https://l2tools.org/api/mcp",
  "require_approval": "never"
}

Clients can also discover the transport through server.json and inspect every REST operation through OpenAPI 3.1.

Stable GET examples

• Search NPCs

  /api/v1/interlude/npcs?query=zaken

• NPC record

  /api/v1/interlude/npcs/29022

• NPC x1 drops

  /api/v1/interlude/npcs/29022/drops

• Soul Crystal progression

  /api/v1/interlude/tools/soul-crystal?npcId=29022

• XP levels

  /api/v1/interlude/tools/xp?fromLevel=60&toLevel=65

Rate limits

REST API traffic is limited per client IP to 10 requests per second with a burst of 30. MCP traffic is limited to 4 requests per second with a burst of 12 and 20 concurrent connections. A limited request receives HTTP 429; clients should cache stable records and retry with backoff.

Contract rules

• Numeric game IDs remain stable identifiers; names and slugs are presentation fields.
• All probabilities are percentages in the range 0–100 and identify their x1 interpretation.
• Large integers are serialized as JSON numbers only when safe, otherwise as decimal strings.
• Errors use an explicit machine-readable code and never silently switch chronicles.
• Public tools are deterministic and have no account or write side effects.