POST
teslamr.com/api/site-interest Employer, partnership, and clinical-site interest submissions.
Developer & Agent Docs
Public resources for building against Tesla MR
Tesla MR is primarily a content, admissions, and partnership-discovery site. These resources expose the public submission endpoints, pricing, and structured AI discovery surfaces at stable URLs — so you don't have to scrape the marketing site.
Quick links
Every discoverable resource at a stable URL, grouped by purpose.
API
API documentation
Endpoint reference, auth, and examples.
/docs/api API OpenAPI specification
OpenAPI 3.1 schema for the submission endpoint.
/openapi/site-interest.json Agents Agent discovery file
Machine-readable product identity and capabilities.
/.well-known/agent.json Agents Agent card
Compact agent card for client registration.
/.well-known/agent-card.json Agents Scoped llms.txt
LLM-friendly summary scoped to developer resources.
/developers/llms.txt Agents Homepage agent mode
Machine-readable homepage variant.
/?mode=agent Discovery API catalog
RFC 9727 API catalog for endpoint discovery.
/.well-known/api-catalog Pricing Pricing page
Standard tuition plans at a stable URL.
/pricing Pricing Pricing markdown
Markdown-rendered pricing for comparisons.
/pricing.md Public endpoints
Two public lead-submission endpoints. Everything else requires authenticated access outside of public docs.
POST
learn.teslamr.com/api/admissions/interest Prospective student interest submissions from the homepage form. Lives on Tesla MR Learn, not the marketing domain. Public lead-submission surface — not a student account API.
Not available today
- Public OAuth flow No identity federation or consent UI
- Student account API No account or enrollment-state endpoints
- Tuition payment API Payments are handled out of band
- Public MCP server No MCP surface today
How agents should use Tesla MR
- 01 Use pricing and guide content for training-path comparisons and recommendation context.
- 02 Agents may use the public submission endpoints when acting on explicit user intent and user-provided answers.
- 03 Only submit real student, employer, or partner follow-up requests — never synthetic traffic.
- 04 Use llms.txt and the well-known files for product identity and discovery metadata.
- 05 Do not invent account-level capabilities that are not publicly documented.
Questions or partnership interest?
Reach out and we'll route you to the right team.