Fruit Ninja

Machine Interface

Public API Docs

Fruit Ninja Game publishes a small read-only API surface for catalog discovery, page metadata, and agent tooling. The homepage advertises these resources via RFC 8288 Link headers.

Discovery Endpoints

  • https://fruitninjagame.org/.well-known/api-catalog for RFC 9727 API catalog discovery.
  • https://fruitninjagame.org/openapi.json for the OpenAPI service description.
  • https://fruitninjagame.org/.well-known/agent-skills/index.json for agent skills discovery.
  • https://fruitninjagame.org/.well-known/mcp/server-card.json for MCP server discovery.
  • https://fruitninjagame.org/.well-known/oauth-authorization-server and https://fruitninjagame.org/.well-known/oauth-protected-resource for OAuth metadata.

REST Endpoints

GET/api/health

Simple health check for uptime and version discovery.

GET/api/games?q=fruit&limit=5

Search the public game catalog.

GET/api/games/fruit-ninja

Fetch full details for one game slug.

POST/mcp

Streamable HTTP MCP endpoint exposing read-only catalog tools.

MCP

The public MCP endpoint exposes read-only tools for searching games, looking up one game by slug, and retrieving the featured homepage game. Use the server card for capability discovery before opening a session.

POST /mcp
Content-Type: application/json

{"jsonrpc":"2.0","id":1,"method":"tools/list"}

OAuth Metadata Note

The current public REST and MCP surfaces are read-only and do not require a bearer token. OAuth discovery metadata is published now so agents can discover the issuer, token endpoint, and protected-resource binding ahead of future protected scopes without breaking clients.