User-Agent + telemetry
Set a custom User-Agent so abuse triage can find your traffic quickly. Every integration should identify itself with a unique, versioned agent string.
Why it matters
When Meridian receives a flood of requests from an unknown source, our abuse triage team needs to distinguish your integration from malicious traffic in seconds. A custom User-Agent makes that possible. Without one, your traffic blends into the noise and risks being rate-limited or blocked alongside bad actors.
Format
Use the pattern product/version (vendor/comment). The product name must start with meridian- so our filters can group all Meridian-originated traffic.
Examples
meridian-python/1.0 (acme/web)Python SDK v1.0 deployed by Acme Corp for their web dashboard.
meridian-go/2.1 (initech/backend)Go client v2.1 running in Initech's backend services.
meridian-cli/0.9 (dev-local)CLI tool during local development. The comment helps us distinguish dev traffic from production.
Enforcement
Requests without a meridian- prefixed User-Agent receive a stricter rate limit and may be dropped entirely during incidents. Set the header on every request — our edge inspects it before any other processing.
Quick start
import requests
headers = {
"Authorization": "Bearer <your-key>",
"User-Agent": "meridian-python/1.0 (acme/web)"
}
resp = requests.get(
"https://api.getnimbus.net/v1/licenses",
headers=headers
)