Late Api
ListedProvides API guidance and assistance for agent workflows.
Install on your platform
late-api. zernio-dev/zernio-api has no skill named "late-api" any more. It was renamed, moved or deleted upstream.We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-09-28. We don't show a command we know will fail.
What we know about this skill
Publisher
getlate-dev
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: zernio.com.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
zernio.comundeclaredWhat it found (3 of 118)
- README.md:54contacts zernio.com
const response = await fetch('https://zernio.com/api/v1/posts', { - SKILL.md:18contacts zernio.com
curl -X POST https://zernio.com/api/v1/profiles \ - SKILL.md:23contacts zernio.com
curl "https://zernio.com/api/v1/connect/twitter?profileId=PROFILE_ID" \
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned getlate-dev/late-api at 6a8356f4f8.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 6a8356f4f8
- Manifest
- SKILL.md
- Scanned
- 27 files, 2,712 lines
About this skill
What it does
This skill provides guidance and assistance for interacting with the Late API, enabling AI agents to schedule posts across 13 social media platforms. The API allows developers to programmatically manage profiles, connect accounts via OAuth (including Bluesky app passwords and Telegram bot tokens), create and schedule posts, and access analytics data. The base URL for the API is https://zernio.com/api/v1 and documentation can be found at zernio.com/docs.
When to use it
- Automating social media posting schedules across multiple platforms.
- Connecting new social media accounts to a scheduling system.
- Retrieving analytics data for YouTube daily views or LinkedIn performance.
- Managing queued posts and configuring slots within the API.
- Troubleshooting errors related to publishing or authentication.
Key capabilities
- Scheduling posts across 13 platforms (Twitter/X, Instagram, Facebook, LinkedIn, TikTok, YouTube, Pinterest, Reddit, Bluesky, Threads, Google Business, Telegram, Snapchat).
- OAuth account connection flows.
- Management of API keys and authentication.
- Access to platform-specific data and limitations.
- Webhook configuration and signature verification.
- Media upload functionality with presigned URLs.
Example prompts
- "Create a post for Twitter/X, Instagram, and Facebook with the content 'Hello!'."
- "Connect my Twitter account using OAuth."
- "What are the supported media formats for YouTube posts?"
- "Show me the error codes related to publishing failures."
Tips & gotchas
- You will need a valid API key (
YOUR_API_KEY) to interact with the Late API. - Refer to the rule files (e.g.,
rules/authentication.md,rules/posts.md) for detailed documentation on specific functionalities and limitations. - OAuth flows require additional steps beyond simple API calls, as indicated in the
rules/connect.mdfile.