docs(bridge-api): NEAR Intents routing provider + supported matrix endpoint - #19
Conversation
…, live supported matrix endpoint Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016qMKQzEapJkLUJnRPByRX8
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3df99c1d4e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| * The response always echoes the **resolved** rail in `provider` (never `auto`) and in `feeInfo.provider`, so you can show users which rail and fee applied (e.g. "0.1% via Rozo" / "0.3% via NEAR Intents"). | ||
| * `near` orders can currently settle only on Base (`8453`), Solana (`900`) and Stellar (`1500`). Asking for `near` on a route it cannot serve returns `400 ROUTE_NOT_SUPPORTED_BY_PROVIDER` — it is never silently downgraded. | ||
| * `near` deposit addresses are single-use and expire; never reuse one. | ||
| * Use [`GET /payment-api/payments/supported`](supported-tokens-and-chains.md#live-supported-matrix) to discover which rails serve which chains and tokens. |
There was a problem hiding this comment.
The repository advertises docs/openapi-v2.0.0.yaml as its downloadable API specification, but this feature is added only to the prose documentation: the spec still has no /payments/supported path, no provider property on CreatePaymentRequest, and no provider/feeInfo fields on PaymentResponse. Consumers generating clients from that contract therefore cannot call the discovery endpoint or set and read the newly documented routing fields; update the OpenAPI document alongside these examples.
Useful? React with 👍 / 👎.
1 participant
Documents the new optional
providerfield (auto | rozo | near), thefeeInfo.providerblock, NEAR-specific error codes, and the liveGET /payment-api/payments/supporteddiscovery endpoint. Backend shipped in RozoAI/rozo-intents-api#273.🤖 Generated with Claude Code
https://claude.ai/code/session_016qMKQzEapJkLUJnRPByRX8