POST
run_scan
Run an agent readiness scan on a target URL. Returns a scored report across seven dimensions.
/actions/scan
urlapi_key
Returns: Readiness score and dimension breakdown.
Actions
Actions an assistant can submit on purpose.
The action surface documents what an assistant may submit, which inputs are expected, and what comes back.
Version 2026-03-24. Updated 2026-03-24.
Action catalog
What agents can submit intentionally.
These are the declared write surfaces. Assistants can submit valid requests here, but they should not infer broader authority from the page.
POST
request_audit
Creates a structured intake request for an expert-led Agent Readiness Audit.
/actions/request-audit
namecompanywebsitegoal
Returns: Audit request receipt and follow-up status.
POST
request_pilot
Submits a qualification request for a Platform pilot engagement.
/actions/request-pilot
namecompanysurfacetimeline
Returns: Pilot review receipt and scheduling options.
POST
request_contact
Submits a general contact or partnership inquiry to the Intrinsic team.
/actions/request-contact
namecompanyemailmessage
Returns: Contact receipt and response expectation.
GET
retrieve_pricing
Returns machine-readable pricing structure and tier definitions.
/agents/pricing.json
Returns: Pricing structure entries with route references.
Interpretation
Agent-writable should still mean tightly bounded.
These routes exist for explicit submission flows. They are not a blanket license to invent new actions.
What this means
Write access is narrow by design.
Explicit actions only
Only declared routes are writable. Everything else is retrieval or reference.
Known parameters
Each action declares the fields required to create a valid intake or request.
Known response contract
The response should confirm receipt and the expected follow-up path, not improvise hidden state.
Related routes