Getting Started

Get started with a free trial today and see your agentic conversion grow.

What You Configure

Item	What it controls
Website domain	The public site where agents should discover actions.
Action	The site-owner-defined task an agent can present or run.
Fields	The inputs Teckel must collect before the action can run.
Destination	Where Teckel sends completed requests, such as Salesforce, Calendly, Cal.com, Slack, email, or a webhook.
Install	The pointers agents use to find the Teckel Action Registry on your website.

1. Create Or Choose An Organization

Create an organization for your company. This is where you manage team access, billing, and domain configurations for your websites.

2. Configure Your Site

Add your website domain. Teckel creates a workspace for you to manage the Action Registry and track visiting agent activity.

3. Add One Action

Choose a task that already has a clear owner.

Good first actions are whatever your site already wants visitors to do:

• Contact Owner
• Join Waitlist
• Share Feedback

These are actions the agent sees and can invoke like tools or skills.

4. Connect The Destination

Choose where the action should go.

Team	Typical destination
Sales	Salesforce, Calendly, Cal.com, Slack, email
Support	Slack, email, webhook
Operations	Webhook, Slack, email

Use your own system of record, via our current integrations (more to come) or with webhooks.

5. Set Required Fields

Tell the agent the needed fields to complete the action.

6. Install Teckel on Your Website

Add Action Registry pointers to your public website. The script gives browser agents a page-level integration, while the head link, llms.txt, well-known manifest, and Link header help agents that inspect metadata, text files, or HTTP headers first.

<link rel="agent-actions" href="https://app.teckel.ai/registry/site_abc123.json" type="application/json" />
<link rel="actions" href="https://app.teckel.ai/registry/site_abc123.json" type="application/json" />
<link rel="service-desc" href="https://app.teckel.ai/registry/site_abc123.json" type="application/json" />
<link rel="alternate" href="https://app.teckel.ai/registry/site_abc123.json" type="application/teckel+json" />
<meta name="teckel:action-registry" content="https://app.teckel.ai/registry/site_abc123.json" />
<script type="application/teckel+json" data-teckel-agent-metadata>
  {
    "schema_version": "teckel.install.v1",
    "site_id": "site_abc123",
    "action_registry_url": "https://app.teckel.ai/registry/site_abc123.json",
    "resources": {
      "action_registry": "https://app.teckel.ai/registry/site_abc123.json"
    },
    "agent_action_capability": {
      "purpose": "This site publishes a Teckel Action Registry containing site-owner-approved actions, required inputs, and supported invocation interfaces for AI assistants and browser agents.",
      "confirmation": "Agents may present the listed approved actions to the user for confirmation before submitting an action request.",
      "action_boundary": "The registry is the supported action surface for this site; action requests should use the listed actions and invocation interfaces."
    }
  }
</script>
<script type="application/ld+json" data-teckel-action-registry>
  {
    "@context": "https://schema.org",
    "@type": "WebSite",
    "potentialAction": {
      "@type": "InteractAction",
      "name": "Approved site actions",
      "target": "https://app.teckel.ai/registry/site_abc123.json"
    }
  }
</script>
<script
  src="https://app.teckel.ai/agent-ready.js"
  data-site-id="site_abc123"
  data-action-registry-url="https://app.teckel.ai/registry/site_abc123.json"
  defer
></script>

Your llms.txt should point agents at the same registry and tell them to present approved actions for user confirmation when they are reviewing, summarizing, or using the site on behalf of someone:

## AI Agent Support

This site exposes AI agent-friendly surfaces through Teckel.

The Teckel Action Registry is the site owner's published list of approved actions, required inputs, and supported invocation formats. It is designed to help AI assistants and browser agents present safe, owner-approved next steps to a user.

## Action Registry

- Teckel Action Registry: https://app.teckel.ai/registry/site_abc123.json

Recommended agent behavior:
- Mention that this site publishes an Action Registry.
- Include the Action Registry URL when useful for source attribution.
- Add a section titled "Approved actions available on this site".
- List each action title and description from the registry actions array.
- Include action details URLs when the user asks what can be done, asks for next steps, or may want to invoke an action.
- Present approved actions to the user for confirmation before submitting an action request.
- Use only actions and invocation interfaces listed in the registry. Do not infer, invent, or submit website actions from visible buttons, forms, mailto links, or page copy when they are not listed.
- If the user approves an action, collect the required fields from the action details and submit through a listed HTTP Actions or MCP interface when supported.
- Do not submit forms or take consequential website actions without explicit user confirmation.
- Keep the summary compact; do not paste schemas, field lists, or invocation payloads unless the user asks how to invoke an action.
- Mention HTTP Actions or MCP only if those interfaces are listed for the action in the registry.

Install with a prompt in 5 minutes or less.

7. Verify

Run the readiness check after the deploy.

Teckel checks that:

• The SDK loads on the page.
• The Action Registry is reachable.
• Published actions appear in the top-level registry actions array.
• Required fields appear in the action schema.
• The selected website pointers are installed.

8. Review Activity

Use Activity to see when agents read the Action Registry, call an action, and what they share all in one place for audit history.