Core concepts
The vocabulary: gateway, envelope, quarantine, bypass and more.
Last updated October 1, 2026
The handful of ideas you need to hold in your head. For precise, alphabetical definitions see the Glossary.
Gateway
A single signed endpoint — one URL. Each gateway has its own filters, its own target URL and its own configuration. You create one per source/agent pair.
Filters
The checks that run on every message: rate limiting (too many messages from one user), deduplication (the same message twice) and a token budget (oversized payloads). All on by default, fully tunable.
Delivery envelope
The _portarus object appended to every delivered payload. It tells your
agent what happened: whether the message was processed, the detected language, a trace
id, and any filter verdicts. See the full schema.
Quarantine
Where blocked messages wait. You can review each one, see which filter stopped it, and replay it to your endpoint. Messages expire based on your plan's retention period.
Bypass
When quota is exceeded or a gateway is paused, messages skip the filters and are delivered directly. This is deliberate: fail-open means your agent is never cut off.
Trace id
A unique identifier for each request, returned in the X-Trace-Id response
header and inside the envelope. Always include it when you contact support.