Install Jentic One Beta

Connect the Taggbox Widget API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Taggbox Widget 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%2Ftaggbox.com%2Ftaggbox" | 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%2Ftaggbox.com%2Ftaggbox" | 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 Taggbox Widget API.

Get gallery information

Manage social media data programmatically

Integrate Taggbox Widget API into automated workflows

Query and filter Taggbox Widget API records by parameters

Monitor Taggbox Widget API operational status and events

GET STARTED

Start building with Taggbox Widget API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Taggbox Widget API for, with concrete tasks.

★ Social Media Operations

Use the Taggbox Widget API to perform social media operations programmatically. The API provides 3 endpoints covering core functionality including get gallery information, get feed information for a gallery, get posts for a gallery.

Call GET /galleries to get gallery information

Automated Feeds Management

Automate feeds operations by combining multiple Taggbox Widget API endpoints. Agents can get feed information for a gallery and then get posts for a gallery in a single workflow.

Call GET /feeds to get feed information for a gallery, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Taggbox Widget 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 apiKey tokens manually.

Search Jentic for 'get gallery information', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

3 endpoints — taggbox widget api for retrieving gallery, feed, and post information from social media aggregation widgets.

METHOD

PATH

DESCRIPTION

GET

/galleries

Get gallery information

GET

/feeds

Get feed information for a gallery

GET

/posts

Get posts for a gallery

GET

/galleries

Get gallery information

GET

/feeds

Get feed information for a gallery

GET

/posts

Get posts for a gallery

Why Jentic?

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

Setup

Wiring the Taggbox Widget API by hand means appending your user_key to the query string on every request and paging through galleries, feeds, and posts yourself. Through Jentic you install once, import the Taggbox Widget API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Taggbox's read calls pass their gallery target as a query parameter rather than a path resource, so limit the agent to the operations it needs, such as listing galleries or feeds, rather than to any one gallery. Every operation the agent can run is one you chose to allow.

Credential isolation

Your Taggbox user key 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 'get gallery information' or 'list social feeds', and Jentic returns the matching Taggbox operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Taggbox Widget API through Jentic.

What authentication does the Taggbox Widget API use?

The Taggbox Widget API uses an API key passed in the `user_key` query. 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 get gallery information with the Taggbox Widget API?

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

What are the rate limits for the Taggbox Widget 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 get gallery information through Jentic?

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

How many endpoints does the Taggbox Widget API have?

The Taggbox Widget API exposes 3 endpoints covering feeds, galleries, posts operations.

Can I limit what my agent is allowed to do with the Taggbox Widget API?

Yes. Because you run Jentic One yourself, your own rules decide which Taggbox operations and credentials the agent may use. The Taggbox Widget API exposes three read calls, GET /galleries, GET /feeds, and GET /posts, that take their gallery target as a query parameter rather than a path resource, so you scope the agent by allowing only the operations it needs, such as listing galleries or feeds. Every operation the agent can run is one you chose to allow.

Taggbox Widget API

Name: Taggbox Widget API
Brand: Taggbox Widget API
Availability: InStock

Official vendor OpenAPI document · agent-readySocial MediaSocial PublishingapiKey3 EndpointsREST

For Agents

Programmatically get gallery information, get feed information for a gallery. Covers 3 operations with apiKey authentication.

Use for: I need to gallery information, I want to feed information for a gallery, Search for posts for a gallery, List all records from Taggbox Widget API

Not supported: Does not handle payments, communications, or crm - use for social media only.

Taggbox Widget API for retrieving gallery, feed, and post information from social media aggregation widgets. The API exposes 3 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Taggbox Widget API to your agent

Capabilities

Start building with Taggbox Widget API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Taggbox Widget API