protocols.io Integration
Use the exact endpoint version documented for each operation. The official API
landing page is still titled “API v3,” but its maintained sections mix v3
and v4. There is no single safe /api/v3 base to apply to every resource.
This skill was refreshed against official sources on 2026-07-23.
Operating Contract
- Start offline. Validate credentials/configuration, saved JSON, pagination, or a write plan before making a request.
- Require
--executefor network reads. Bundled write tooling has no execution mode. - Read only named variables. Never inspect the full environment, search
for
.envfiles, traverse parent directories, or accept a token/secret in a command argument, request file, log, traceback, or output. - Use official HTTPS hosts only. Core reads use
www.protocols.io(the docs also show the bare host). Organization exports use the customer's explicit<subdomain>.protocols.ioorigin. Reject redirects and disable ambient proxy discovery so bearer credentials are not routed unexpectedly. - Distinguish public content from anonymous API access. A client token is documented for pu…
