canonical: https://jentic.com/apis/seebot.run/seebot-run

# SeeBotRun Link API

SeeBotRun Link API for managing shortened URLs, branded domains, QR codes, and platform tracking. The API exposes 37 endpoints secured with bearer authentication.

## For AI agents

Programmatically create domain, list all domains. Covers 37 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for analytics only.

## Capabilities

- Create domain
- List all domains
- Get domain by ID
- Update domain
- Delete domain

## Use cases

### Analytics Operations

Use the SeeBotRun Link API to perform analytics operations programmatically. The API provides 37 endpoints covering core functionality including create domain, list all domains, get domain by id.

Example prompt: Call POST /domains to create domain

### Automated Domains Management

Automate domains operations by combining multiple SeeBotRun Link API endpoints. Agents can list all domains and then get domain by id in a single workflow.

Example prompt: Call GET /domains to list all domains, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SeeBotRun Link API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'create domain', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/domains` | Create domain |
| GET | `/domains` | List all domains |
| GET | `/domains/{id}` | Get domain by ID |
| PUT | `/domains/{id}` | Update domain |
| DELETE | `/domains/{id}` | Delete domain |
| POST | `/links` | Create link |
| GET | `/links` | List all links |
| GET | `/links/{id}` | Get link by ID |

## Key resources

- **Domains** — Domain management
- **Links** — Link management
- **Tags** — Tag management
- **Reports** — Report management
- **Attributes** — Attribute management

## Why Jentic

- **Setup:** Wiring the SeeBotRun Link API by hand means obtaining its bearer token, threading it onto every call, and building each domain and link request across its wide surface yourself. Through Jentic you install once, import SeeBotRun Link from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** SeeBotRun puts the domain and link ids in the URL path (`/domains/{id}` and `/links/{id}`), so a rule can pin your agent to one domain: it can read and create links under it and nothing else. You choose the operations it may call, so destructive ones like deleting a domain or a link are not included unless you add them.
- **Credential handling:** Your SeeBotRun token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a short link' or 'list domains', and Jentic returns the matching SeeBotRun operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the SeeBotRun Link API use?

The SeeBotRun Link API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create domain with the SeeBotRun Link API?

Yes. Use the POST /domains endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SeeBotRun Link API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create domain through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create domain'. Jentic returns the matching SeeBotRun Link API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the SeeBotRun Link API have?

The SeeBotRun Link API exposes 37 endpoints covering domains, links, tags operations.

### Can I limit what my agent is allowed to do with the SeeBotRun Link API?

Yes. Jentic One is self-hosted by you, so your own rules decide which SeeBotRun operations and credentials the agent may use. Because SeeBotRun puts the domain and link ids in the URL path, such as `/domains/{id}` and `/links/{id}`, you can pin the agent to a single domain and allow it to read and create links under that domain and nothing else. You pick the exact operations it may call, so destructive ones like deleting a domain or a link are excluded unless you explicitly add them.
