Skip to content

OpenRAG is a comprehensive, single package Retrieval-Augmented Generation platform built on Langflow, Docling, and Opensearch.

Python
31.1 KB
Raw Blame
{"id": "key-rotate", "query": "How do I swap out an API key without causing downtime?", "expected_files": ["api-keys.md"], "expected_text": "overlap window", "tags": ["semantic"], "expected_answer": "Select Rotate in Settings → API keys, then deploy the replacement key while the old key still works during the overlap window (24 hours by default, configurable from 1 hour to 7 days). Check Last used and revoke the old key when it is no longer used, or let the window expire."}
{"id": "key-leaked", "query": "One of our keys was pushed to a public repo, what should we do right now?", "expected_files": ["api-keys.md"], "expected_text": "Revoke immediately", "tags": ["semantic"], "expected_answer": "Choose Revoke immediately so the compromised key stops working at once, without a rotation overlap. Revocation is permanent; create a new key instead."}
{"id": "key-scopes", "query": "What scopes can I give an API key?", "expected_files": ["api-keys.md"], "expected_text": "destinations:manage", "tags": ["keyword"], "expected_answer": "The available scopes are events:write, events:read, destinations:manage, replay:run and workspace:admin."}
{"id": "key-prefix-ci", "query": "What is a key starting with rwk_ci_ used for?", "expected_files": ["api-keys.md"], "expected_text": "Automation key", "tags": ["exact-token"], "expected_answer": "rwk_ci_ identifies an automation key for pipelines and infrastructure tooling. It cannot send events."}
{"id": "sig-verify", "query": "How can my server confirm that a webhook really came from Relaywise and was not forged?", "expected_files": ["signing-secrets.md"], "expected_text": "HMAC-SHA256", "tags": ["semantic"], "expected_answer": "Compute HMAC-SHA256 over <timestamp>.<raw body> with the destination's signing secret and compare the lowercase hexadecimal result to the v1 signature using constant-time comparison. Use the unparsed body and reject timestamps more than five minutes old."}
{"id": "sig-roll", "query": "How do I change the secret used to sign deliveries, and how long do the old and new ones both work?", "expected_files": ["signing-secrets.md"], "expected_text": "72 hours", "tags": ["semantic"], "expected_answer": "Choose Roll secret in the destination's Signing settings and update your endpoint to the new secret. Deliveries carry both signatures for 72 hours, after which the previous secret is discarded; Expire previous secret can drop a compromised old secret immediately."}
{"id": "sig-max-age", "query": "How old can a signed request be before I should refuse it?", "expected_files": ["signing-secrets.md"], "expected_text": "five minutes", "tags": ["semantic"], "expected_answer": "Reject a signed request whose timestamp is more than five minutes old to limit replay attacks."}
{"id": "sig-whsec", "query": "Where do I find the whsec_ value for a destination?", "expected_files": ["signing-secrets.md"], "expected_text": "Reveal", "tags": ["exact-token"], "expected_answer": "Open the destination, go to Settings → Signing, and select Reveal to see its whsec_ signing secret. Each destination has its own secret and revealing it is audited."}
{"id": "sso-setup", "query": "How do we let staff log in to the console with their company accounts?", "expected_files": ["single-sign-on.md"], "expected_text": "identity provider", "tags": ["semantic"], "expected_answer": "Configure SAML 2.0 or OpenID Connect with your identity provider under Settings → Security → Single sign-on; SSO is available on Scale and Enterprise. Verify your email domain before enforcing Require SSO; OpenID Connect is preferred when both protocols are available."}
{"id": "sso-lockout", "query": "If our identity provider goes down, can anyone still get into the console?", "expected_files": ["single-sign-on.md"], "expected_text": "break-glass", "tags": ["semantic"], "expected_answer": "Owners retain a break-glass login using a password and a one-time code even when SSO is required. Keep at least two Owners in case the identity provider fails."}
{"id": "sso-offboarding", "query": "How is someone's access removed automatically when they leave the company?", "expected_files": ["single-sign-on.md"], "expected_text": "SCIM", "tags": ["semantic"], "expected_answer": "Enable SCIM provisioning with your identity provider. Unassigning or deactivating a user ends console access within a few minutes and revokes their personal access tokens."}
{"id": "session-length", "query": "How long before the console logs me out?", "expected_files": ["single-sign-on.md", "configuration-reference.md"], "tags": ["semantic", "multi-doc"], "expected_answer": "Console sessions last 12 hours by default and idle sessions end after 60 minutes. Enterprise can configure the overall session length from 1 hour to 30 days with console.session_hours."}
{"id": "dlq-purge-who", "query": "Who is allowed to empty a dead-letter queue?", "expected_files": ["roles-and-permissions.md", "dead-letter-queue.md"], "tags": ["keyword", "multi-doc"], "expected_answer": "Only Admins and Owners may purge a destination's dead-letter queue; Developers and Viewers cannot."}
{"id": "viewer-payloads", "query": "Can a read-only user see the contents of events?", "expected_files": ["roles-and-permissions.md"], "expected_text": "Payload access", "tags": ["semantic"], "expected_answer": "Viewers see metadata but not event bodies by default. An Admin must separately enable Payload access on the member to let them read bodies; payload views are audited."}
{"id": "invite-expiry", "query": "How long does a team invitation link stay valid?", "expected_files": ["roles-and-permissions.md"], "expected_text": "valid for 7 days", "tags": ["semantic"], "expected_answer": "An invitation link is valid for 7 days. Resending it from Settings → Members invalidates the original link."}
{"id": "ownership-transfer", "query": "How do I hand a workspace over to a colleague?", "expected_files": ["roles-and-permissions.md"], "expected_text": "last Owner", "tags": ["semantic"], "expected_answer": "An Owner must first promote the colleague to Owner and confirm they can log in, then demote themselves. Relaywise refuses to remove the last Owner."}
{"id": "retry-schedule", "query": "How many times will a failed webhook be attempted, and over how long?", "expected_files": ["delivery-retries.md"], "expected_text": "27 hours", "tags": ["semantic"], "expected_answer": "By default an event gets up to 8 total delivery attempts over a little more than 27 hours. Waits after the first attempt are 30 seconds, 2 minutes, 10 minutes, 1 hour, 3 hours, 8 hours and 15 hours, with up to 20 percent jitter."}
{"id": "cfg-max-attempts", "query": "What is the default for delivery.max_attempts?", "expected_files": ["delivery-retries.md", "configuration-reference.md"], "expected_text": "delivery.max_attempts", "tags": ["exact-token", "multi-doc"], "expected_answer": "delivery.max_attempts defaults to 8 total attempts. Its allowed range is 1 to 20, and 1 disables retries."}
{"id": "circuit-breaker", "query": "What happens when most requests to one endpoint start failing?", "expected_files": ["delivery-retries.md"], "expected_text": "degraded", "tags": ["semantic"], "expected_answer": "If more than half of a destination's deliveries fail within ten minutes, it becomes degraded and is slowed to one request per second while events queue. It returns to normal after two minutes of all deliveries succeeding."}
{"id": "gone-410", "query": "What does Relaywise do if my endpoint answers 410 Gone?", "expected_files": ["delivery-retries.md", "dead-letter-queue.md"], "expected_text": "410 Gone", "tags": ["exact-token", "multi-doc"], "expected_answer": "A 410 Gone stops retries for that event and pauses the destination so its URL can be checked. The event goes to the destination's dead-letter queue."}
{"id": "duplicate-events", "query": "Why did my endpoint get the same event twice?", "expected_files": ["delivery-retries.md", "troubleshooting.md"], "tags": ["semantic", "multi-doc"], "expected_answer": "Retries can deliver an event twice when the endpoint processed it but its response was lost. Store event IDs from Relaywise-Event-Id and skip repeats; also check whether two routes target the same destination if duplicates are frequent."}
{"id": "ordered-delivery", "query": "Can I make sure events for one customer are delivered in sequence?", "expected_files": ["delivery-retries.md"], "expected_text": "ordering key", "tags": ["semantic"], "expected_answer": "Enable ordered delivery on the route and choose an ordering key such as customer ID. A failing event holds back later events with that key until it succeeds or exhausts its attempts."}
{"id": "destination-auto-disabled", "query": "Why was my destination turned off without anyone touching it?", "expected_files": ["delivery-retries.md", "troubleshooting.md"], "tags": ["semantic", "multi-doc"], "expected_answer": "Relaywise disables a destination after five consecutive days without a successful delivery and emails the Admins. Fix and re-enable it, then replay the events collected in its dead-letter queue."}
{"id": "dlq-what", "query": "Where do events go once every delivery attempt has been used up?", "expected_files": ["dead-letter-queue.md"], "tags": ["semantic"], "expected_answer": "Events that exhaust all delivery attempts move to the destination's dead-letter queue, where they can be inspected and replayed after fixing the cause."}
{"id": "dlq-retention-team", "query": "On the Team plan, how long are undeliverable events kept before they are removed?", "expected_files": ["dead-letter-queue.md"], "expected_text": "14 days", "tags": ["semantic"], "expected_answer": "Team retains events in the dead-letter queue for 14 days from entry. After that they are deleted and cannot be replayed."}
{"id": "dlq-replay-other-destination", "query": "How do I use rwctl dlq replay to resend failed events to a new endpoint?", "expected_files": ["dead-letter-queue.md"], "expected_text": "dst_9x1aa", "tags": ["exact-token"], "expected_answer": "Add --to with the new destination ID, for example rwctl dlq replay --destination dst_4h7q2 --since 2h --to dst_9x1aa."}
{"id": "replay-header", "query": "How can my endpoint tell that a delivery is a replay?", "expected_files": ["dead-letter-queue.md"], "expected_text": "Relaywise-Replay", "tags": ["semantic"], "expected_answer": "Replayed deliveries carry Relaywise-Replay: true and retain the original event ID."}
{"id": "ingest-rate", "query": "How fast am I allowed to send events on each plan?", "expected_files": ["rate-limits.md"], "expected_text": "events per second", "tags": ["semantic"], "expected_answer": "Sustained ingest limits across all workspace sources are 10 events per second on Sandbox, 200 on Team, 2,000 on Scale and contract-defined on Enterprise. Bursts can reach twice the sustained rate for up to 10 seconds."}
{"id": "err-4290", "query": "RW-4290", "expected_files": ["rate-limits.md", "error-codes.md"], "expected_text": "RW-4290", "tags": ["exact-token", "multi-doc"], "expected_answer": "RW-4290 means the workspace exceeded its rate limit and the event was not accepted. Wait for the Retry-After time before retrying."}
{"id": "payload-max-size", "query": "What is the largest event body I can send?", "expected_files": ["rate-limits.md"], "expected_text": "256 KB", "tags": ["semantic"], "expected_answer": "One event payload may be at most 256 KB; larger payloads are rejected with RW-4130. Store larger data elsewhere and send a link."}
{"id": "batch-size", "query": "How many events fit in one batch request?", "expected_files": ["rate-limits.md"], "expected_text": "500 events", "tags": ["keyword"], "expected_answer": "A batch may contain up to 500 events, with a total request size limit of 5 MB. Every event still counts toward the ingest rate limit."}
{"id": "err-3002", "query": "What does error RW-3002 mean?", "expected_files": ["error-codes.md"], "expected_text": "TLS handshake failed", "tags": ["exact-token"], "expected_answer": "RW-3002 means the TLS handshake failed because the endpoint certificate has expired, is self-signed or does not match the hostname."}
{"id": "err-5004", "query": "RW-5004", "expected_files": ["error-codes.md", "transformations.md"], "expected_text": "RW-5004", "tags": ["exact-token", "multi-doc"], "expected_answer": "RW-5004 means a transformation returned an invalid value. It must return an object, or null to drop the event."}
{"id": "err-2031", "query": "Why was my destination URL rejected with RW-2031?", "expected_files": ["error-codes.md", "network-security.md"], "expected_text": "RW-2031", "tags": ["exact-token", "multi-doc"], "expected_answer": "RW-2031 means the destination URL resolves to a private or reserved address. Destinations must be public unless private connectivity is configured through an Enterprise private link."}
{"id": "err-7001", "query": "What causes RW-7001?", "expected_files": ["error-codes.md", "regions.md"], "expected_text": "RW-7001", "tags": ["exact-token", "multi-doc"], "expected_answer": "RW-7001 means the request used an ingest hostname in a different region from the workspace. Use the workspace's regional ingest hostname."}
{"id": "cfg-concurrency", "query": "Which setting limits how many requests hit my endpoint in parallel?", "expected_files": ["configuration-reference.md"], "expected_text": "delivery.max_concurrency", "tags": ["semantic"], "expected_answer": "delivery.max_concurrency limits simultaneous deliveries to one destination. It defaults to 25 and allows values from 1 to 500."}
{"id": "cfg-dedupe-window", "query": "ingest.dedupe_window_seconds", "expected_files": ["configuration-reference.md"], "expected_text": "ingest.dedupe_window_seconds", "tags": ["exact-token"], "expected_answer": "ingest.dedupe_window_seconds discards events whose idempotency key was already seen within the configured window. It defaults to 0 and accepts 0 to 3600 seconds."}
{"id": "cfg-explain", "query": "How do I find out which level a setting's value is coming from?", "expected_files": ["configuration-reference.md", "cli-reference.md"], "expected_text": "rwctl config explain", "tags": ["semantic", "multi-doc"], "expected_answer": "Run rwctl config explain <key> --destination <id> to see the effective value and where it came from. Destination values override workspace defaults and route values override destination values."}
{"id": "schema-validation", "query": "Can incoming payloads be checked against a schema and refused when they don't match?", "expected_files": ["configuration-reference.md"], "expected_text": "ingest.schema_validation", "tags": ["semantic"], "expected_answer": "Set ingest.schema_validation to reject to refuse payloads that do not match their registered event-type schema. warn accepts them with a warning, and off disables checking."}
{"id": "filter-wildcard", "query": "How do I send every kind of invoice event, including nested types, to one endpoint?", "expected_files": ["event-filtering.md"], "expected_text": "invoice.**", "tags": ["semantic"], "expected_answer": "Use the route filter type matches \"invoice.**\" to match invoice event types including nested names. A single * matches only one dotted segment."}
{"id": "filter-missing-field", "query": "What happens when a filter refers to a field the event doesn't have?", "expected_files": ["event-filtering.md"], "expected_text": "it is not an error", "tags": ["semantic"], "expected_answer": "A comparison against a missing field evaluates to false; it is not an error. Use exists(...) when field presence matters."}
{"id": "unrouted-events", "query": "What happens to an event that no route picks up?", "expected_files": ["event-filtering.md"], "expected_text": "unrouted", "tags": ["semantic"], "expected_answer": "An event matching no route is marked unrouted and stored in event history for the usual retention period, but nothing is delivered. It still counts toward the monthly quota."}
{"id": "route-fan-out", "query": "How many endpoints can one route deliver to?", "expected_files": ["event-filtering.md"], "expected_text": "up to 20 destinations", "tags": ["semantic"], "expected_answer": "One route can deliver to up to 20 destinations, each with independent delivery and retries."}
{"id": "strip-fields-before-delivery", "query": "How can I strip card numbers out of events before they are forwarded to a partner?", "expected_files": ["transformations.md"], "expected_text": "card_number", "tags": ["semantic"], "expected_answer": "Use a route transformation to remove sensitive fields such as card_number before returning the payload to deliver. Storage redaction alone does not change the delivered payload."}
{"id": "transform-network", "query": "Can transformation code call an external API?", "expected_files": ["transformations.md"], "expected_text": "No network access", "tags": ["semantic"], "expected_answer": "No: transformation code runs in a sandbox with no network access, so it cannot make HTTP requests or open sockets."}
{"id": "transform-rollback", "query": "I shipped a broken transformation, how do I go back to the previous one?", "expected_files": ["transformations.md"], "expected_text": "Make active", "tags": ["semantic"], "expected_answer": "Open the transformation's History, choose an earlier version and select Make active. The switch applies to new deliveries within a few seconds; the last 50 versions are retained."}
{"id": "plan-scale-price", "query": "What does the Scale plan cost and how many events come with it?", "expected_files": ["billing-plans.md"], "expected_text": "20 million", "tags": ["keyword"], "expected_answer": "Scale costs $399 per month and includes 20 million events per month. Extra events cost $0.25 per 10,000."}
{"id": "over-quota", "query": "What happens if we send more events in a month than our plan includes?", "expected_files": ["billing-plans.md"], "expected_text": "billed as overage", "tags": ["semantic"], "expected_answer": "Team and Scale accept excess events and bill them as overage unless a hard cap is set. Sandbox has no overage and rejects events after 50,000 until the next month."}
{"id": "spending-cap", "query": "How do I make sure we never get a surprise bill?", "expected_files": ["billing-plans.md"], "expected_text": "hard cap", "tags": ["semantic"], "expected_answer": "Set a hard cap under Settings → Billing → Usage cap. Once usage reaches it, Relaywise rejects new events for the rest of the billing period instead of charging more."}
{"id": "downgrade-timing", "query": "When does a plan downgrade kick in?", "expected_files": ["billing-plans.md"], "expected_text": "end of the current billing period", "tags": ["semantic"], "expected_answer": "A downgrade takes effect at the end of the current billing period, once the workspace fits the lower plan's limits. Retention shortens then and older history is deleted."}
{"id": "nonprofit-discount", "query": "Is there a discount for nonprofits?", "expected_files": ["billing-plans.md"], "expected_text": "50 percent off", "tags": ["semantic"], "expected_answer": "Registered charities and accredited schools and universities get 50 percent off Team and Scale. Apply through support."}
{"id": "card-declined", "query": "What happens if our card is declined?", "expected_files": ["invoices-and-payments.md"], "expected_text": "suspended", "tags": ["semantic"], "expected_answer": "Relaywise immediately emails the billing contact and Owners and retries the charge after 3, 5 and 7 days while service continues normally. If still unpaid after 10 days the workspace is suspended; paying lifts it within minutes, but 30 days after suspension it is closed and its data deleted."}
{"id": "invoice-download", "query": "Where can I download past invoices?", "expected_files": ["invoices-and-payments.md"], "expected_text": "PDF", "tags": ["keyword"], "expected_answer": "Download past invoices as PDFs under Settings → Billing → Invoices."}
{"id": "annual-refund", "query": "Can I get my money back on an annual subscription?", "expected_files": ["invoices-and-payments.md"], "expected_text": "30 days of purchase", "tags": ["semantic"], "expected_answer": "Yearly plans can be refunded in full within 30 days of purchase. After that they run to the end of the term."}
{"id": "pay-by-wire", "query": "Can we pay by wire instead of by card?", "expected_files": ["invoices-and-payments.md"], "expected_text": "bank transfer", "tags": ["semantic"], "expected_answer": "Yearly Scale and all Enterprise workspaces can request bank transfer against an invoice. Those invoices are due within 14 days."}
{"id": "payload-retention-scale", "query": "How long are event bodies stored on the Scale plan?", "expected_files": ["data-retention.md"], "expected_text": "These are maximums", "tags": ["semantic"], "expected_answer": "Scale keeps payloads for up to 30 days and metadata for up to 90 days. These are maximums and retention settings can shorten them."}
{"id": "erasure-request", "query": "A customer asked us to erase their personal data, how do I remove their events?", "expected_files": ["data-retention.md"], "expected_text": "Delete events", "tags": ["semantic"], "expected_answer": "Use the deletion API or Settings → Data → Delete events to select events by time and optionally a payload field and value; one event also has Delete payload. Payloads are removed immediately from the primary store, backups age out within 35 days, and metadata remains unless Delete metadata is selected."}
{"id": "never-store-field", "query": "How do I keep a sensitive field from ever being saved?", "expected_files": ["data-retention.md", "configuration-reference.md"], "expected_text": "retention.redact_fields", "tags": ["semantic", "multi-doc"], "expected_answer": "Add the field's payload path to retention.redact_fields so its stored value becomes [redacted] before storage. The endpoint still receives the original value; use a transformation to remove it from deliveries too."}
{"id": "export-to-own-storage", "query": "Can I keep events for longer than the plan allows by copying them to storage we own?", "expected_files": ["data-retention.md"], "expected_text": "scheduled export", "tags": ["semantic"], "expected_answer": "On Scale or Enterprise, configure a scheduled export under Settings → Data → Export. It writes new events hourly as compressed JSON Lines to your own storage bucket."}
{"id": "replay-event-gone", "query": "Replay fails saying the event isn't available any more, why?", "expected_files": ["data-retention.md", "troubleshooting.md"], "tags": ["semantic", "multi-doc"], "expected_answer": "The payload expired under the workspace's retention policy and has been deleted, even if metadata is still listed, so it cannot be replayed. Longer retention or scheduled exports prevent future loss of the payload."}
{"id": "eu-residency", "query": "We need our data to stay inside the EU, is that possible?", "expected_files": ["regions.md"], "expected_text": "eu-central", "tags": ["semantic"], "expected_answer": "Choose eu-central (Frankfurt) when creating the workspace to keep event data and backups in the EU. Some account information for login and billing is held centrally in the United States, but event data is not."}
{"id": "move-region", "query": "Can I move an existing workspace to another region?", "expected_files": ["regions.md"], "expected_text": "cannot be changed", "tags": ["semantic"], "expected_answer": "An existing workspace's region cannot be changed. Create a new workspace in the target region, export and import configuration, and update senders to its ingest hostname; event history does not move."}
{"id": "firewall-ips", "query": "Which IP addresses do I need to let through our firewall so deliveries arrive?", "expected_files": ["regions.md", "network-security.md"], "expected_text": "rwctl network egress-ips", "tags": ["semantic", "multi-doc"], "expected_answer": "Allow the fixed delivery egress IP addresses for your workspace's region. Find the current list on its Network page or run rwctl network egress-ips, and still verify delivery signatures."}
{"id": "alert-on-failing-endpoint", "query": "How do I get notified when an endpoint starts failing?", "expected_files": ["monitoring-and-alerts.md"], "expected_text": "delivery.success_rate", "tags": ["semantic"], "expected_answer": "Create a rule under Monitoring → Alerts for delivery.success_rate, for example below 95 percent for 15 minutes, scoped to the destination if needed. Choose email, chat webhook, paging or a Relaywise destination for notifications."}
{"id": "metric-dlq-depth", "query": "dlq.depth", "expected_files": ["monitoring-and-alerts.md", "dead-letter-queue.md"], "expected_text": "dlq.depth", "tags": ["exact-token", "multi-doc"], "expected_answer": "dlq.depth is the number of events waiting in a dead-letter queue. Create an alert threshold on it to detect a growing queue."}
{"id": "alert-noise", "query": "How do I stop an alert from notifying us over and over?", "expected_files": ["monitoring-and-alerts.md"], "expected_text": "cooldown", "tags": ["semantic"], "expected_answer": "Set the rule's cooldown, which defaults to 30 minutes and can range from 5 minutes to 24 hours, to suppress repeated notifications. Use Mute during planned work; a longer evaluation window also reduces false alarms."}
{"id": "metrics-history", "query": "How far back do the charts go?", "expected_files": ["monitoring-and-alerts.md"], "expected_text": "13 months", "tags": ["semantic"], "expected_answer": "Metrics remain at one-minute resolution for 7 days and one-hour resolution for 13 months. They contain counts and timings rather than payloads."}
{"id": "audit-who-changed", "query": "How can I find out who changed a destination's URL?", "expected_files": ["audit-log.md"], "expected_text": "destination.url_changed", "tags": ["semantic"], "expected_answer": "Open Settings → Audit log and filter by the destination ID and action destination.url_changed. Entries identify the actor, time, target, source IP and outcome; only Owners and Admins can read the log by default."}
{"id": "audit-retention", "query": "How long is the record of admin actions kept?", "expected_files": ["audit-log.md"], "expected_text": "7 years", "tags": ["semantic"], "expected_answer": "Audit log retention is 30 days on Sandbox, 1 year on Team and Scale, and 7 years on Enterprise. It is independent of event retention."}
{"id": "audit-tamper", "query": "Could an admin cover their tracks by deleting log entries?", "expected_files": ["audit-log.md"], "expected_text": "hash", "tags": ["semantic"], "expected_answer": "Nobody, including Owners and Relaywise staff, can edit or delete audit entries. Each entry hashes the previous one so alterations or removals are detectable."}
{"id": "support-access", "query": "Can Relaywise staff look at our payloads?", "expected_files": ["audit-log.md"], "expected_text": "Support access", "tags": ["semantic"], "expected_answer": "Support cannot see payloads or change configuration by default. An Owner can grant Support access under Settings → Security for 1 hour to 7 days; actions are audited as support with the ticket number."}
{"id": "local-development", "query": "How do I receive webhooks on my laptop while developing?", "expected_files": ["cli-reference.md"], "expected_text": "rwctl listen", "tags": ["semantic"], "expected_answer": "Run rwctl listen --forward-to localhost:4000/webhooks to open a tunnel that forwards events sent with a test key to your laptop. Add --print-secret to test signature verification and Ctrl+C to close the tunnel."}
{"id": "cli-in-pipeline", "query": "How do I authenticate the command-line tool in a CI pipeline?", "expected_files": ["cli-reference.md"], "expected_text": "RELAYWISE_API_KEY", "tags": ["semantic"], "expected_answer": "Set RELAYWISE_API_KEY to an automation key in the pipeline. rwctl uses it instead of a stored browser login when the variable is set."}
{"id": "cli-exit-code-5", "query": "What does exit code 5 from rwctl mean?", "expected_files": ["cli-reference.md"], "expected_text": "Rate limited", "tags": ["exact-token"], "expected_answer": "Exit code 5 means rate limited. Wait before trying the command again."}
{"id": "client-certificates", "query": "Our endpoint requires callers to present a client certificate, is that supported?", "expected_files": ["network-security.md"], "expected_text": "mutual TLS", "tags": ["semantic"], "expected_answer": "Yes: enable mutual TLS on the destination so Relaywise presents a client certificate. Download the CA bundle from the destination's Security tab and configure your server to trust it; certificates renew every 60 days under the same CA."}
{"id": "restrict-senders", "query": "Can I restrict which servers are allowed to send events to us?", "expected_files": ["network-security.md"], "expected_text": "ingest allowlist", "tags": ["semantic"], "expected_answer": "Configure the ingest allowlist under Settings → Security → Ingest allowlist or ingest.allowed_ips with CIDR ranges. Once populated, requests from other addresses are refused before the API key is checked."}
{"id": "enforce-two-step", "query": "How do I force everyone to use two-step login?", "expected_files": ["network-security.md"], "expected_text": "Require two-factor", "tags": ["semantic"], "expected_answer": "An Admin can enable Settings → Security → Require two-factor for password users, who must set up a second factor at their next login. SSO members follow the identity provider's rules instead."}
{"id": "encryption-at-rest", "query": "Is stored data encrypted?", "expected_files": ["network-security.md"], "expected_text": "AES-256", "tags": ["semantic"], "expected_answer": "Stored event payloads, transformation secrets and backups use AES-256 encryption at rest, with keys rotated every 90 days. Enterprise can supply its own encryption key."}
{"id": "nothing-arriving", "query": "My endpoint isn't getting any events, where do I start looking?", "expected_files": ["troubleshooting.md"], "expected_text": "Was the event accepted", "tags": ["semantic"], "expected_answer": "Check Events to confirm acceptance, then check whether the event matched a route and whether the destination is enabled. Open delivery attempts and inspect their status codes or errors to see what the endpoint did."}
{"id": "lost-authenticator", "query": "I lost my authenticator app, how do I get back in?", "expected_files": ["troubleshooting.md"], "expected_text": "second factor", "tags": ["semantic"], "expected_answer": "Ask an Admin to reset your second factor so you can log in again."}
{"id": "first-test-event", "query": "What is the quickest way to send a first test event?", "expected_files": ["getting-started.md"], "expected_text": "202 Accepted", "tags": ["semantic"], "expected_answer": "Create a source, HTTPS destination and connecting route, then create an API key with events:write and POST a JSON event to the source ingest URL using Bearer authentication. A successful request returns 202 Accepted and an evt_ ID; watch its delivery under Events."}
{"id": "source-vs-destination", "query": "What is the difference between a source and a destination?", "expected_files": ["getting-started.md"], "expected_text": "Where events come from", "tags": ["keyword"], "expected_answer": "A source is where events come from and supplies the ingest URL your application posts to. A destination is the HTTP endpoint that receives events, with its own URL, signing secret and delivery settings."}
{"id": "plain-http-destination", "query": "Can a destination use a plain http URL?", "expected_files": ["getting-started.md", "error-codes.md"], "expected_text": "localhost", "tags": ["keyword", "multi-doc"], "expected_answer": "Destination URLs must use HTTPS. Plain HTTP is accepted only for localhost through the development tunnel."}