Can I create a threads media container for text, image, video, or carousel posts with the Threads API?

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

What are the rate limits for the Threads 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 a threads media container for text, image, video, or carousel posts through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a threads media container for text, image, video, or carousel posts'. Jentic returns the matching Threads API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Threads API have?

The Threads API exposes 9 endpoints covering posts, media, insights operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Threads API operations and credentials the agent may use. Since the Threads user id sits in the URL path, such as /{threadsUserId}/threads, you can pin the agent to a single Threads user so it acts only for that account. You also choose the exact operations it may call, so publishing actions like POST /{threadsUserId}/threads_publish or reply moderation stay off unless you add them, letting you allow read-only insights calls on their own.