SignalAF developers

API, MCP, CLI and agent integration

SigRank SignalAF exposes public operator-benchmark data through a versioned REST API, an OpenAPI document, the official sigrank CLI, and Model Context Protocol tools. Public read endpoints do not require credentials. Protected writes use the authentication flow documented in auth.md.

Quickstart

# Read the public leaderboard
curl -s https://signalaf.com/api/v1/leaderboard

# Inspect the API contract
curl -s https://signalaf.com/openapi.json

# Run the official CLI / MCP server
npx sigrank

Developer resources

OpenAPI 3.0

Machine-readable REST API contract

Authentication

OAuth, public reads, protected writes

MCP server

Model Context Protocol setup and tools

MCP manifest

Machine-readable MCP discovery

Agent index

When to use SignalAF and canonical resources

Methodology

Metric definitions and evidence boundary

Authentication

Public leaderboard and operator reads are credential-free. User-authorized writes use Supabase OAuth/session authentication. Bulk corpus access can use an issued API key via x-api-key; there is currently no self-service key issuance UI. See auth.md.

Errors

REST failures use RFC 9457 Problem Details with media type application/problem+json. Every problem includes HTTP status, a stable machine-readable code, human-readable detail, and, when recovery is possible, a hint.

Rate limits

Public list reads use a 60-request, 60-second best-effort per-instance window. Responses expose RateLimit-Policy and RateLimit structured fields, with compatibility RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset fields. A 429 also includes Retry-After.

Versioning and deprecation

Stable REST endpoints are versioned in the URL, currently /api/v1. Breaking contract changes ship under a new major API path. When a v1 operation is scheduled for retirement, SignalAF will return a Deprecation header and an HTTP-date Sunset header on that operation, while the OpenAPI document and this page identify its replacement.

Sandbox

No separate hosted sandbox exists today. For non-mutating integration work, use the public read API or run npx sigrank locally. Do not send test writes to production. A hosted write sandbox is a separate product/infrastructure decision.