Skip to content

Limits & kill switch

Set caps on each key, block repeat posts, and switch off one customer or agent in one call. Postkey enforces it before anything reaches a platform.

  • Post caps per key, per day
  • Spend caps per key, per month
  • Duplicate blocking over a window you choose
  • One call turns a key off, including its queue
limits.tsnode
1// One key per agent, with caps it can't change.2await pk.keys.update("agent_scheduler", {3  dailyPostLimit: 504});5 6// Something's wrong? Off, right now.7await pk.keys.update("agent_scheduler", {8  active: false9});

429 · blocked: daily limit reached

What comes back

{
  "status": "blocked",
  "reason": "daily_limit_reached",
  "message": "agent_scheduler reached its daily limit (50/50)."
}

How it works

  • Caps the key can't raise

    Limits live on the key, set with your account secret. An agent holding the key can't change them.

  • Repeats stopped

    A retry loop sending the same content again gets a clear refusal, not a second post.

  • A real off switch

    Disable one key and it stops now, scheduled posts included. Every other key keeps working.

Works with your stack

  • Your code

    Node and Python SDKs with the same calls, or plain REST from anything that speaks HTTP.

    • Node
    • Python
    • {}REST
    Read the docs
  • No-code tools

    Call the REST API from an HTTP step in n8n, Make or Zapier. Give each workflow its own key.

    • n8n
    • Make
    • Zapier
    Postkey with n8n
  • AI agents & MCP

    The MCP server lets Claude, Cursor and other agent tools post through their own key, with caps they can't change.

    • MCP server
    About the MCP server

Questions

Something not here? Email hello@postkey.dev.

What happens when a key hits its cap?

The post is refused with a plain error saying which limit was hit and when it resets. Nothing reaches the platform.

Do failed posts count toward limits?

No. Only posts that went out count.

Can I turn a key back on?

Yes. Enable it again and it picks up with the same limits and history.

Give everyone who posts their own key.

Get a key, connect an account, send your first request.