~/ domain/garage61.net.mdTHE AGENT-READABLE WEB

garage61.net valid

Garage 61

Garage 61 is a motorsports telemetry platform. Use its documented public API to build integrations with racing data that the authenticated user has permission to access.

Visit publisher ↗

For agents: Motorsports telemetry platform with a documented public OpenAPI for building racing-data integrations, with OAuth2 and personal access token auth and rate limit

motorsports telemetryracing data apiopenapioauth2sim racing

Authority
49 reach 8 · trust 5 · quality 21 · freshness 15
Tier
listed
llms.txt
https://garage61.net/llms.txt
Sections
3
Links
11
Size
2730 bytes
Popularity rank
#243206
Country
Germany
Categories
APIs and SDKs · Automotive
For agents
Interface: a documented API or declared MCP endpoint an agent can call
Audience
developers · agents can: read docs, call api · en
First seen
2026-10-19T10:40:54.426Z
Last checked
2026-10-19T12:06:38.610Z
Badge
Agent Web Map badge for garage61.net

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T15:09:25.183Z. Cached copy · Source on garage61.net

# Garage 61

> Garage 61 is a motorsports telemetry platform. Use its documented public API to build integrations with racing data that the authenticated user has permission to access.

Read the public OpenAPI specification before writing API calls. It is the source of truth for the API server URL, supported operations, parameters, schemas and authentication requirements. The specification can be fetched without authentication and does not require JavaScript.

Use only documented public endpoints. Do not use /api/internal/* or undocumented endpoints used by the website or telemetry agents. Do not reverse-engineer frontend code, inspect website network traffic or guess endpoints to fill gaps in the public API. If a capability is missing from the public specification, explain the limitation and contact Garage 61 rather than falling back to an internal API.

API calls require an API application and an access token. Use a personal access token for your own data, or OAuth2 to access data on behalf of other users. Send the token as Authorization: Bearer TOKEN. Access is limited by application permissions and the user's authorization; there is no API for exporting all users' data.

Respect rate limits. On HTTP 429, wait at least the Retry-After interval before retrying. Cache results, use pagination and avoid excessive polling. The API may change; consult the current specification and changelog.

## API specification

- [Public OpenAPI specification (JSON)](https://garage61.net/api/openapi/v1.json): Machine-readable endpoint reference. Start here and use the server URL declared in the specification.
- [Public OpenAPI specification (YAML)](https://garage61.net/api/openapi/v1.yml): The same specification in YAML format.

## Developer documentation

- [Getting started](https://garage61.net/developer/getting-started): API concepts, limitations and application setup.
- [Authentication](https://garage61.net/developer/authentication): Personal access tokens and OAuth2 configuration.
- [Permissions](https://garage61.net/developer/permissions): Available permissions and scopes.
- [Rate limits](https://garage61.net/developer/rate-limits): Rate limit headers and retry behavior.
- [Endpoint reference](https://garage61.net/developer/endpoints): Human-readable reference for the public API.
- [Webhooks](https://garage61.net/developer/webhooks): Webhook setup and signature validation.
- [Changelog](https://garage61.net/developer/changelog): API changes.

## Optional

- [API applications](https://garage61.net/developer/applications): Manage applications and personal access tokens. Requires sign-in.
- [Contact](https://garage61.net/contact): Ask about missing public API capabilities or integration issues.

Related sites

Other listed sites in APIs and SDKs. See the whole category →

DomainTitleCategoryCountryAuthorityllms.txtllms-full.txtSave
ausca.com Ausca interface AI agents and MCP APIs and SDKs 65 ✓ ✓
agentwebmap.com Agent Web Map interface AI and machine learning AI agents and MCP +1 FR 60 ✓ ✓
wordpress.com WordPress.com interface APIs and SDKs US 75 ✓
hostinger.com Hostinger interface Design Infrastructure +2 73 ✓ ✓
buffer.com Buffer API interface APIs and SDKs Productivity 72 ✓ ✓
openai.com OpenAI Developers interface Education Developer tools +3 72 ✓ ✓
sentry.io Sentry interface DevOps and observability APIs and SDKs +1 US 72 ✓ ✓
stripe.com Stripe interface Finance and payments APIs and SDKs IE 72 ✓

Machine-readable: GET /v1/resolve?q=garage61.net · GET /v1/domain/garage61.net · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Own or manage this website?

If you own or manage garage61.net, you can update its listing and review file health, discovery activity and score history.

Manage this listing — optional

What verification unlocks

See how your site is discovered—and control what agents see.

  • Control what agents see

    Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.

  • Make your profile eligible for search

    A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.

  • Appear in our llms-full.txt

    Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.

Free. No account registration, backlink or payment required. Public discovery remains available without verification.

Verify your website—free

Preview the owner dashboard · All verification benefits

Let your coding agent verify it

If your coding agent is authorized to manage this website, paste these instructions into it.

Claim my listing on Agent Web Map for garage61.net:
1. POST https://agentwebmap.com/v1/sites/garage61.net/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://garage61.net/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/garage61.net/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/garage61.net).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.

agent web map / a clearer way in.API & MCP · Contact