Skip to main content
Templates are predefined browser workflows with input schemas. Run a template in an existing session with POST /v1/template. Templates are provided by Tilion. They are not exposed as separate tools in the hosted MCP catalogue.

GET /v1/templates

The catalogue, with each template’s input schema. Auth: Bearer API key. Request: optional query parameters category (one of job-automation, data-extraction, form-filling, monitoring, research, commerce, other) and tag. Response: The current catalogue has two templates, both of which take a LinkedIn li_at session cookie (trimmed):
Errors: 401 invalid key; 422 when a query parameter has the wrong type. Free, no session needed.

POST /v1/template

Run a template by name in a session’s browser. Same envelope, auth, limits and billing as POST /v1/agent. Auth: Bearer API key. Request: Response: the POST /v1/agent envelope. task echoes name, steps is always [] and meta always {}; data is the template’s own result. linkedin_session returns authenticated (true or false) with a reason (ok, cookie_not_applied, auth_wall, checkpoint, navigation_failed), and linkedin_extract adds target, final_url, a best-effort structured data (name, headline, location, about, experience, education, skills, connections, followers, any JSON-LD, page_type), the page as markdown, and raw_html_len. On a template timeout the answer is ok: false, error: "template_timeout: did not finish in N s". A required input missing (no browser is touched):
An unknown name:
Errors: Notes:
  • Timeout: the template’s declared limit, 180 s for both current templates, never more than 300 s.
  • Billing: one action credit per run that finishes without a timeout.
  • Validation happens before the session is looked up, so a bad body is refused in under half a second.