SeeBotRun Link API

Name: SeeBotRun Link API
Brand: SeeBotRun Link API
Availability: InStock

✓ Official Vendor SpecAnalyticsWeb Analyticsbearer37 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the SeeBotRun Link API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SeeBotRun Link API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fseebot.run%2Fseebot-run" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fseebot.run%2Fseebot-run" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with SeeBotRun Link API.

Create domain

List all domains

Get domain by ID

Update domain

GET STARTED

Start building with SeeBotRun Link API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use SeeBotRun Link API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

37 endpoints — seebotrun link api for managing shortened urls, branded domains, qr codes, and platform tracking.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using SeeBotRun Link API through Jentic.

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.

SeeBotRun Link API

Connect the SeeBotRun Link API to your agent

Capabilities

Start building with SeeBotRun Link API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs