Can I list available segments with the Tradable Bits API?

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

What are the rate limits for the Tradable Bits 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 list available segments through Jentic?

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

How many endpoints does the Tradable Bits API have?

The Tradable Bits API exposes 38 endpoints covering apps, crm, entertainment operations.

Can I limit what my agent is allowed to do with the Tradable Bits API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Tradable Bits operations and credentials the agent may use. Because the fan id sits in the URL path (/v1/crm/fans/{fan_id}), you can pin the agent to a specific fan and only the operations it needs there, such as reading or searching fan records. You choose which operations it may call, so a destructive action like deleting a fan (DELETE /v1/crm/fans/{fan_id}) is not available to the agent unless you explicitly add it.