Developers

Use the index from software

VibeLeaderboard exposes its public catalog and Intel through ordinary REST, an OpenAPI contract, a read-only MCP server, an agent skill, and RSS. Public reads need no API key. Account-specific operations and catalog writes require authentication. Start with the interface that matches your runtime, then use the same IDs to move between search results, tool details, and cited Intel.

Interfaces

OpenAPI 3.1

Typed REST contract for client generation and function calling.

Agent guide

Plain-text examples, field semantics, rate limits, and when-to-use guidance.

MCP discovery

Streamable HTTP endpoint and tool inventory.

Agent skill

Installable instructions for tool and Intel discovery.

RSS

One permalinked Daily Brief edition per item.

Quick start

curl 'https://www.vibeleaderboard.ai/api/v1/apps?search=local+coding+agent&limit=5'

curl https://www.vibeleaderboard.ai/api/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Versioning and deprecation

Stable REST operations carry a major version in the path, beginning with /api/v1. Backward-compatible fields may be added within v1. A breaking contract change requires a new major path.

Before removing a stable version, VibeLeaderboard publishes migration guidance, sends the RFC 9745 Deprecation header, and announces a dated Sunset header at least 90 days before removal. Rate-limited responses include structured RateLimit-Policy and RateLimitfields. A rejected request also includes Retry-After.

Support

Send reproducible API or MCP issues through the contact page. Include the endpoint, response status, and a redacted request. Catalog corrections and new entries use the same evidence-first review process as the public site.