For developers
API keys for /mcp-pro.
Higher rate limits and deeper retrieval for agents that call Garage Door Science tools in production. Email magic-link signup. No credit card.
Tiers at a glance
| Capability | /mcpPublic | /mcp-proPro · bearer key |
|---|---|---|
| Auth | ||
| Auth | None | Authorization: Bearer gds_live_…, a free key from the form above |
| Rate limit | ||
| Rate limit | 60 a minute, 2,000 a day, per IP | 240 a minute, 10,000 a day, per IP |
| Tools you can call | ||
| Tools you can call | 10 of 12. retrieveLabContext needs a key. | 11 of 12. identifyOpener needs the Technician plan, which is not part of the free key. |
| Retrieval depth | ||
| Retrieval depth | Not available without a key | retrieveLabContext returns up to 10 results a call |
| REST | ||
| REST | /api/v1/<tool> with no key. Same limits. Browser calls from other sites need a Turnstile token. | /api/v1/<tool> with your key. Same limits. No Turnstile. |
| OpenAPI | ||
| OpenAPI | /openapi.json, one spec for both tiers | /openapi.json, try calls at /developers/api |
Per-tool details
Built from the live tool registry, so it matches what the endpoints allow. retrieveLabContext needs a key, and identifyOpener needs the Technician plan; the rest are open on the public tier within the general rate limits.
| Tool | Public | Pro | Notes |
|---|---|---|---|
diagnose | Yes | Yes | — |
routeByZip | Yes | Yes | — |
getDoorStyles | Yes | Yes | — |
getActivePromotions | Yes | Yes | — |
getInspectionReferencePhotos | Yes | Yes | — |
getLab | Yes | Yes | — |
getLabEmbed | Yes | Yes | — |
retrieveLabContext | No, needs a key | Yes | Up to 10 results a call on pro. |
visualDiagnose | Yes · 20/day per IP | Yes · 100/day per IP | A daily photo cap on top of the general rate limit. |
identifyOpener | No, needs a key | No, needs the Technician plan | — |
costEstimate | Yes | Yes | — |
submitInspection | Yes | Yes | — |
10-second start
Find the local installer for a ZIP code with routeByZip. Both run as pasted, with no key. Run the fetch from a server or Node 18+: a browser on another site needs a Turnstile token on the public tier.
To use your pro limits, add Authorization: Bearer gds_live_… with your own key; the reply then also carries "priority": true.
curl -s https://garagedoorscience.com/api/v1/routeByZip \
-H 'content-type: application/json' \
-d '{"zipOrLocation": "89101"}'Response
{
"covered": true,
"region": "Las Vegas Valley",
"regionKey": "nevada.las_vegas",
"partnerId": "<partner id>",
"partner": {
"displayName": "<partner name>",
"phone": "<partner phone>",
"url": "https://garagedoorscience.com/go/<partner>",
"schedulerUrl": "https://garagedoorscience.com/go/<partner>-schedule",
"canEmbedScheduler": true,
"reviews": null,
"reviewsLine": null
},
"leadHeat": "warm"
}The partner, phone and links depend on the ZIP you send. leadHeat repeats the one you sent: hot for an emergency, warm for a replacement, cold for research. It is warm when you send none.
How it works
- Enter your email above. We send a magic-link.
- Click the link within 15 minutes to verify.
- Generate a key in the dashboard. Plaintext is shown once.
- Send as
Authorization: Bearer gds_live_...tohttps://garagedoorscience.com/mcp-pro(MCP) or/api/v1/<tool>(REST). - Try calls in the browser at /developers/api (interactive OpenAPI docs).
Need the free tier instead?
The public endpoint at https://garagedoorscience.com/mcp requires no auth — just point any MCP-compatible client at it. All details on the agent docs page.
Recent changes
- getDoorStyles: sourced prices only, R-value filter removed
- visualDiagnose and submitInspection: what they store and who gets emailed
- /mcp now lists only the tools the public tier can call
- routeByZip marks pro callers with a priority flag
- identifyOpener and opener spec data need the Technician plan
- getLabEmbed: an iframe snippet for any lab
The full list, with what each change means for your calls, is at /developers/changelog. Subscribe to the JSON feed for a programmatic reader.
What can I build with this?
Four distinct consumer patterns — Claude Desktop, ChatGPT Custom GPT, LangChain agents, and contractor-site embed widgets — with runnable recipes for each. See /developers/use-cases and the cookbook repo.