An API key resolves exactly one connected Chirp profile. Clients never submit profile IDs.
Give agents Chirp's Threads intelligence.
One scoped API surface for personal-baseline analytics, Scout opportunity discovery, next-move recommendations, and confirmation-gated scheduling. Built for external agents without exposing Threads access tokens, billing controls or internal admin APIs.
Read scopes are separate from scheduling. Write access is never granted by default.
External calls record the source, action, scope, result, and timestamp without storing raw secrets.
Keys can be revoked instantly from Chirp Settings.
Bearer API keys
Create a key in Chirp Settings. The full secret is shown once and the stored record contains a one-way digest. Only provide a key to an agent or client you trust.
Authorization: Bearer chirp_live_… X-SkillChirp-Client: muse
Minimum access by default
analytics:readAccount summary and personal performance baseline
scout:readSearch Scout for conversations worth joining
recommendations:readRead data-backed next moves
schedule:writePrepare and confirm scheduled posts; opt-in only
Small surface, clear jobs
/api/v1/chirp/account/Connected account summary/api/v1/chirp/performance/Personal baseline and measured post performance/api/v1/chirp/next-move/Recommendations plus saved high-fit Scout opportunities/api/v1/chirp/scout/Search conversations worth joining/api/v1/chirp/schedule/prepare/Validate and preview a schedule action; does not write/api/v1/chirp/schedule/confirm/Confirm a signed preview within 10 minutesAsk for the next move
curl https://skillchirp.onrender.com/api/v1/chirp/next-move/ \ -H "Authorization: Bearer $CHIRP_API_KEY" \ -H "X-SkillChirp-Client: muse"
Jobs the connector is designed to handle
01How is my latest Threads post performing compared with my normal baseline?
02Find 3 high-opportunity Threads conversations about AI SaaS that are worth joining.
03Based on my recent Threads performance, what should I do today?
04Analyze my Threads account and tell me which content pattern is working best.
05Prepare a Threads post based on my strongest recent content pattern and schedule it for tomorrow morning.
Scheduling is prepare → review → confirm
The scheduling scope is opt-in. The prepare endpoint validates the request and returns a preview plus a short-lived confirmation token without creating a scheduled post. The confirm endpoint accepts only a matching, unexpired, single-use token for the same account and API key.
Stable, agent-readable failures
External API errors use a bounded object with a machine-readable code, a human-readable message, and a retryable flag. Upstream Threads errors are normalized rather than returning access tokens or raw provider payloads.
{
"error": {
"code": "RATE_LIMITED",
"message": "Too many requests. Try again shortly.",
"retryable": true
}
}Access can be shut off without disconnecting Threads
Revoke an external API key from Chirp Settings to stop that key authenticating immediately. Disconnecting Threads also prevents connected external keys from accessing Chirp while the account is disconnected.
Public review links
PrivacyTermsSupportOpenAPIThis API is connector-ready infrastructure. It does not claim SkillChirp is approved, listed or featured in Muse. Submission and Meta review remain separate.