Support
Frequently asked questions
The ones we get asked most — the free tier, billing, limits, delivery, and security. Still stuck? Email us.
Getting started
- What is EchoRelay?
- EchoRelay is the relay layer between your callers and your services. One authenticated request is validated, rate-limited, and fanned out to every service you connect — webhooks, APIs, events — with at-least-once delivery (every request is retried until it lands) and a dead-letter queue for anything that still fails. You never build that plumbing.
- Do I need to write any code?
- No. You configure lines, endpoints, and targets from the dashboard — or hand the whole setup to an AI agent over our MCP server. Callers then POST to your endpoint and EchoRelay does the rest.
- What is a line?
- A line is a version of your API — like v1 or v2. Under the hood it is just a named group of endpoints with its own key and docs, so you do not have to use it for versions: split by environment, by team, or however suits you. It shows up in your request path, e.g. /v1/your-endpoint.
- How do I get started?
- Create a free account (no card), add a line (your API version, e.g. v1) and an endpoint, point it at one or more targets, and mint a project key. You are relaying in minutes.
Free tier & pricing
- Is there really a free tier?
- Yes — unlimited relayed requests, no credit card, no monthly quota. Free is rate-limited, not metered: a generous rate that is boosted for your first 90 days, then a steady free rate. You get the same delivery stack as paid.
- What happens when I run out of credits?
- On the free tier there is nothing to run out of — it is rate-limited, not credit-billed. On paid plans, when your balance reaches zero, calls return HTTP 402 until you top up or your billing cycle resets. Your projects, keys, and config are never touched.
- Do my credits expire?
- Prepaid packs are valid for 12 months from purchase. Subscription credits reset each billing cycle — unused allowance does not carry over.
- How are credits counted?
- You only pay for successful deliveries. Each delivery is 1 credit — one per target when a request fans out, plus 1 more per 64 KB of payload. Deliveries that fail on our side are never charged.
- I have prepaid credits and I subscribe — what happens?
- Your spend follows this order automatically: (1) your monthly subscription allowance is spent first — it resets each cycle and you should burn it before it expires; (2) once the allowance is gone, requests draw from your prepaid balance, oldest credits first; (3) once prepaid is exhausted, subscribers accrue billable overage at their plan rate. You will get an email at each step. Prepaid customers without a subscription stop at 0 — we never charge automatically without prior agreement.
- What is the rate limit for prepaid (no subscription)?
- Prepaid customers in credit get up to 500 requests per minute (RPM) — a comfortable steady rate for most workflows. Raise that ceiling to 1,000 RPM with a Pro subscription, or 5,000 RPM with Scale.
- Can I change plans or cancel anytime?
- Yes — upgrade, downgrade, or cancel anytime from your dashboard. Prepaid has no recurring commitment; subscriptions stay active through the period you have already paid for.
Payment
- What payment methods do you accept?
- Card, PayPal, and local methods such as BLIK and iDEAL, depending on your country — handled by our payment provider at checkout. The free tier needs no payment method at all.
Limits & throughput
- What are the rate limits?
- Free: a steady free rate, lifted for your first 90 days. Prepaid (in credit, no subscription): up to 500 requests per minute (RPM). Pro: up to 1,000 RPM. Scale: up to 5,000 RPM. Enterprise: custom. All limits are ceilings, subject to fair use; your exact current rate always shows on your dashboard, and you can raise it with RPM add-ons on Pro or Scale.
- How many targets can one request fan out to?
- A single endpoint can fan out to many targets in parallel, each with its own authentication, headers, and retry budget. The per-request limits cover all but the largest platforms; Enterprise lifts them further.
Delivery & reliability
- What delivery guarantees do I get?
- At-least-once delivery on every tier. Each relay is retried automatically, spaced further apart each time; anything still failing lands in a per-project dead-letter queue you can inspect and replay. Duplicate deliveries are prevented automatically (idempotency keys).
- What happens if one of my targets is down?
- We retry automatically, spacing attempts further apart. If the target is still unreachable after the retry budget, the delivery moves to your dead-letter queue, where you can inspect the payload and replay it once the target recovers — nothing is silently dropped.
- Does EchoRelay keep my real servers hidden?
- Yes. Callers connect to EchoRelay, never to your infrastructure. Your origin stays off the map, and flood or abuse traffic hits us first.
Security
- How is my data secured?
- Inbound API keys are stored as SHA-256 hashes, never in plaintext. Outbound credentials can be encrypted with AES-256-GCM — we store them but cannot read them. Every payload is validated against your schema before anything is delivered.
- Can I bring my own authentication to my targets?
- Yes. Outbound auth — Bearer tokens, API keys, custom headers — is configured per target and applied at delivery, including encrypted secrets. Inbound auth uses a project key you mint and rotate yourself.
Account & support
- Where do my requests run?
- Production runs in the EU (Hetzner, Nuremberg) today, with additional regions on the roadmap.
- How do I get support?
- Email [email protected]. Enterprise plans get priority response times agreed in your contract.