Regional Research

Coming soon — staging prototype; not currently available for paid production research.

This page documents the verified current behavior of the xrplme.online regional research route. The route exists in the codebase but is feature-flagged OFF and is not publicly routed. Nothing on this page is an offer of a live paid service.

Status

Item	Current state
Route	`/rr/v1/research` — not publicly exposed
Feature flag	`XRPLME_REGIONAL_PAID_ROUTE` — disabled (unset)
Live requests	Not accepted; the route is inert while the flag is off
Availability	Coming soon — staging prototype

Verified scope and limits

Parameter	Verified value
Accepted countries	`vietnam`, `japan`, `singapore` (3)
Maximum countries per request	3
Accepted dimensions	`formation`, `immigration`, `labor`, `operating_environment` (4)
Maximum dimensions per request	4
Roadmap dimensions (rejected)	`tax`, `foreign_ownership`, `permits`, `economy`
Objective maximum length	300 characters
Route timeout	45 seconds (returns 504 on timeout)
Output cap	262144 bytes (256 KB)
Rate limiting	Per-key: 10/minute, 100/day

Safety and integrity behavior

Injection rejection — the free-text objective is screened against instruction-like markers and markup (for example ignore previous, system prompt, <script, ```, template braces, control characters). A conservative filter: some legitimate objectives containing those markers are rejected by design.
Redaction — sensitive values are redacted before logging; the route does not log wallet addresses or secrets.
Qualitative comparability mode — cross-country output is presented in qualitative mode; it does not assert a numeric ranking across countries.
Fixture versus live — the route can read sanitized fixture data for development; fixture output is not live data and is labelled as such.

Payment boundary

When (and only when) the feature is enabled, the route uses an x402-style flow: an unpaid request returns an invoice/quote with the payment requirements, and a paid request is only fulfilled after the payment is verified and settled on a validated ledger. Verification requires a validated tesSUCCESS transaction; an unvalidated or failed transaction does not release the report. While the feature flag is unset, no payment path executes at all.

Not offered