1. Read evidence
Responses preserve their source, tier, status, and recorded time when available. Treat missing or unknown verification time as unknown—not current.
Developer platform
Evidence you can inspect.
Create and control a guide without an account.
Use public Tesla evidence in your workflow, then create a partner guide directly with its public name and Tesla referral URL. No sign-in or Clerk account is required.
OpenAPI 3.0 contract LLM discovery text2. Create privately
Public POST /api/v1/partners creates a guide anonymously and returns agent_token and management_capability once. Save them immediately.
3. Work within scope
read reads guide, kit, and aggregate activity; write updates guide details and drafts; publish authorizes publication. The management capability can issue a replacement scoped token.
Authorization and safe automation
The anonymous create response returns agent_token exactly once; pass it as Authorization: Bearer …. It also returns management_capability; use that private capability in X-Partner-Management-Capability to issue a new scoped token. A private browser management link is /partners/recover#<management_capability>. Anyone holding that link or capability can control the guide, so keep it private and never place it in a referral, public page, analytics event, or support ticket. A scoped agent may perform later workflow steps autonomously only within its scopes until expiry or revocation. It must not exceed those scopes or treat a draft/preview as public.
Publication is intentionally explicit: use the documented publish operation only with a key that has the publish scope. Send an Idempotency-Key for every mutation; retry that key only with the same route and exact body.
Keys never grant Tesla-account access. Do not send Tesla credentials, personal referral tokens, buyer contact information, or claims about purchases or Tesla rewards.
Evidence interpretation
Source hierarchy: official Tesla material is the primary source; government and regulator material follows; retained secondary news and market context follows last. A source tier says where a claim came from, not that it was freshly checked.
Status and time: consume the returned evidence status and observed/verified timestamp. The daily-evidence-build worker is a separate process that an operator must explicitly configure; it is not provisioned by this public API. Its due-source run is not a blanket freshness claim and does not automatically publish catalog changes.
Operations in this deployment
The list below is rendered from the same OpenAPI document served by the API. Request and response schemas, Bearer security, standard errors, idempotency rules, and executable examples are authoritative in that contract.
| Method | Path | Purpose | Access |
|---|---|---|---|
POST | /api/v1/agent-keys | Issue a one-time scoped token with a management capability | management_capability |
GET | /api/v1/evidence | Read retained evidence claims and their provenance | public |
POST | /api/v1/guide/results/preview | Preview a result without recording buyer data | read |
GET | /api/v1/partner | Read the key owner's partner and published philosophy | read |
PATCH | /api/v1/partner | Update key owner's partner | write |
POST | /api/v1/partners | Create an accountless partner guide and one-time private capabilities | public |
POST | /api/v1/philosophy/drafts | Save immutable private draft | write |
POST | /api/v1/philosophy/preview | Preview an unpublished philosophy | read |
POST | /api/v1/philosophy/publish | Publish immutable philosophy version | publish |
GET | /api/v1/reports/activity | Read all-time aggregate accepted activity; no custom date ranges | read |
GET | /api/v1/share-kit | Read owner share-kit text and paths | read |
GET | /api/v1/sources | Read the fixed public evidence-source policy and live source status | public |
Try the stdlib example
python examples/create_partner_guide.py --help starts with anonymous guide creation, captures the returned token in memory, creates a draft, requests a preview, and only publishes when --publish is supplied. It can also retrieve the share kit and aggregate report. It turns the returned private management capability into a recovery link to save securely.
Evidence worker setup
Autoscale does not automatically provision a scheduler for this project. After applying the evidence schema, an operator may explicitly deploy a separate process named daily-evidence-build with uv run python scripts/run_evidence.py --loop. Check /api/v1/sources for each source’s returned status before describing any evidence as fresh.