Race Entry
This API was designed specifically for the Director software to allow certain timers and directors integration into our Race Entry data with the Director. It provides programmatic access to events, registrations, participants, teams, results, check-in PINs, and club memberships, with temporary key/secret authentication issued via a login endpoint.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Race Entry the way a machine reads it — 23 machine-readable artifacts across 16 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Race Entry scores 37.9/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Race Entry
Each block below is one kind of artifact we hold for Race Entry. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 16
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Race Entry Event API
The Event API from Race Entry — 3 operation(s) for event.
Race Entry Get Category Teams API
The Get Category Teams API from Race Entry — 1 operation(s) for get category teams.
Race Entry Get Event Categories API
The Get Event Categories API from Race Entry — 1 operation(s) for get event categories.
Race Entry Get Event Participants API
The Get Event Participants API from Race Entry — 1 operation(s) for get event participants.
Race Entry Get Event Pin API
The Get Event Pin API from Race Entry — 1 operation(s) for get event pin.
Race Entry Get Event Questions API
The Get Event Questions API from Race Entry — 1 operation(s) for get event questions.
Race Entry Get Event Teams API
The Get Event Teams API from Race Entry — 1 operation(s) for get event teams.
Race Entry Get Events API
The Get Events API from Race Entry — 1 operation(s) for get events.
Race Entry Login API
The Login API from Race Entry — 1 operation(s) for login.
Race Entry Memberships API
The Memberships API from Race Entry — 2 operation(s) for memberships.
Race Entry Result API
The Result API from Race Entry — 2 operation(s) for result.
Race Entry Set Event App Access API
The Set Event App Access API from Race Entry — 1 operation(s) for set event app access.
Race Entry Set Event Pin API
The Set Event Pin API from Race Entry — 1 operation(s) for set event pin.
Race Entry Update Event Participant API
The Update Event Participant API from Race Entry — 1 operation(s) for update event participant.
Race Entry Upload API
The Upload API from Race Entry — 1 operation(s) for upload.
Race Entry User API
The User API from Race Entry — 1 operation(s) for user.
Scroll within the panel for all 16 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Race Entry Software API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Race Entry Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Race Entry Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Race Entry — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 2
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/race-entry · machine-readable index on apis.io