For Agents
Programmatically schedule a post, connect social account via oauth. Covers 5 operations with bearer authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Zernio Social Media 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%2Fzernio.com%2Fzernio" | shStep 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%2Fzernio.com%2Fzernio" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Zernio Social Media API.
Schedule a post
Connect social account via OAuth
Get engagement analytics
Configure webhook notifications
GET STARTED
Use for: I need to schedule a post, I want to connect social account via oauth, Search for engagement analytics, Find all configure webhook notifications
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
Zernio (formerly Late/getlate) unified social media API for scheduling posts, managing conversations, analytics, and webhook notifications across 14+ platforms. The API exposes 5 endpoints secured with bearer authentication.
List inbox conversations
Patterns agents use Zernio Social Media API for, with concrete tasks.
★ Communications Operations
Use the Zernio Social Media API to perform communications operations programmatically. The API provides 5 endpoints covering core functionality including schedule a post, connect social account via oauth, get engagement analytics.
Call POST /posts to schedule a post
Automated Analytics Management
Automate analytics operations by combining multiple Zernio Social Media API endpoints. Agents can connect social account via oauth and then get engagement analytics in a single workflow.
Call GET /connect/{platform} to connect social account via oauth, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Zernio Social Media 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 'schedule a post', load the operation schema, and execute with Jentic-managed credentials
5 endpoints — zernio (formerly late/getlate) unified social media api for scheduling posts, managing conversations, analytics, and webhook notifications across 14+ platforms.
METHOD
PATH
DESCRIPTION
/posts
Schedule a post
/connect/{platform}
Connect social account via OAuth
/analytics
Get engagement analytics
/webhooks/settings
Configure webhook notifications
/inbox/conversations
List inbox conversations
/posts
Schedule a post
/connect/{platform}
Connect social account via OAuth
/analytics
Get engagement analytics
/webhooks/settings
Configure webhook notifications
/inbox/conversations
List inbox conversations
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Zernio Social Media API by hand means carrying its bearer token on every request, coding post creation, platform connection, and inbox handling on zernio.com/api/v1 yourself. Through Jentic you install once, import Zernio Social Media from the API Directory, store the token once, and your agent calls it.
Permission scoping
Zernio carries the post content in the request body rather than a resource id in the URL path, so limit the agent to the operations it needs, such as creating a post or reading analytics. You leave out webhook settings unless the agent is meant to change them.
Credential isolation
Your Zernio 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 'schedule a post' or 'read post analytics', and Jentic returns the matching Zernio Social Media operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Zernio Social Media API through Jentic.
What authentication does the Zernio Social Media API use?
The Zernio Social Media 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 schedule a post with the Zernio Social Media API?
Yes. Use the POST /posts endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Zernio Social Media 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 schedule a post through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'schedule a post'. Jentic returns the matching Zernio Social Media API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Zernio Social Media API have?
The Zernio Social Media API exposes 5 endpoints covering analytics, connections, inbox operations.
Can I limit what my agent is allowed to do with the Zernio Social Media API?
Yes. Because you run Jentic One yourself, your own rules decide which Zernio operations and credentials the agent can use, so you can allow only what a task needs, such as scheduling posts with POST /posts or reading engagement analytics with GET /analytics. You can withhold the webhook settings operation (POST /webhooks/settings) unless the agent is meant to change delivery configuration, and leave out account connection at GET /connect/{platform} when it is not required. The stored bearer token is injected only for the calls you permit, so a scheduling agent cannot reach the inbox or reconfigure webhooks.