Pricing
Port packages and request bundles with clear upgrades. Developer-first, cache-friendly APIs.
- Standardized JSON/CSV
- Hourly freshness targets
- Email support (best-effort)
- Freshness (p95) ≤ 2h on key ports
- Cache-friendly endpoints (ETag/304)
- Slack/Email weekly summaries
- Priority support & success
- Alerts & webhooks included
- Extended history & index deltas
What’s included
Comparable metrics across regions, one contract, one schema.
Published SLO, with benchmarks for key ports.
ETag/304, CSV/JSON, examples in cURL/JS/Python.
100+ ports, dedicated instances/SLA, or redistribution terms.
FAQ
Is there a free trial? What are the limits?⌄
Yes. 14 days with up to 5 ports and fair quota. Same API as paid tiers.
How is rate limiting enforced?⌄
Roughly 60 rpm per key with short burst x5. SDKs include backoff & retry.
What happens on overage?⌄
For v1 we auto-upgrade to the next tier to keep your jobs running. No surprise per-call fees.
Do you offer refunds or proration?⌄
Monthly can cancel anytime to stop next cycle. Annual follows fair-use terms; talk to us for proration.
Is there a yearly discount?⌄
Yes — pay 10 months, get 12 months (applied at checkout).
How is billing handled?⌄
Stripe in USD with Stripe Tax for VAT/GST. Invoices emailed and downloadable from the portal.
What's your freshness and latency SLO?⌄
Covered ports target freshness p95 ≤ 2h and API latency p95 < 300ms, 99.9% SLA on Pro.
How many ports are covered today? Can you add new ones?⌄
Live 50+ now (67 in P1 scope). We can onboard additional ports in ~2–4 weeks, same schema & SLO.
Do CSV and JSON return the same data?⌄
Yes. CSV mirrors JSON fields. CSV responses send Cache-Control and ETag for 304 savings.
How should I use caching?⌄
Respect Cache-Control: public, max-age=300 and use ETag/If-None-Match for revalidation; SDKs handle this.
What does the error body look like?⌄
{ code, message, request_id, hint }. We also return x-request-id header for tracing.