Public resources¶
Products and APIs¶
| Resource | URL |
|---|---|
| Nexa DEX | dex.vsnexa.com |
| Nexa DEX identity | /.well-known/nexa-dex.json |
| Swap & Bridge guide | docs.vsnexa.com/dex |
| Aggregator API | api.vsnexa.com |
| Aggregator API guide | docs.vsnexa.com/aggregator-api |
| Aggregator discovery | /.well-known/nexa-aggregator.json |
| Aggregator OpenAPI | /openapi.json |
| Solver API | solver.vsnexa.com |
| Documentation | docs.vsnexa.com |
Use the Nexa access guide to choose between the direct web interface, the Aggregator API, and the solver integration surface.
Canonical machine endpoints¶
| Resource | URL |
|---|---|
| Solver discovery | /.well-known/nexa-solver.json |
| On-chain fingerprint | /.well-known/nexa-onchain-discovery.json |
| Standards manifest | /.well-known/nexa-standards.json |
| OpenAPI | /openapi.json |
| Solver discovery projection | /api/v6/solver-discovery |
| Signed Feed | /api/v6/solver-feed |
| Feed events | /api/v6/solver-feed/events |
Endpoint templates for route detail and permit status are defined in discovery and OpenAPI. Use concrete IDs from verified responses; do not copy placeholders into requests.
Repository and packages¶
- Public README
- Public integration manifest
- Mainnet V6 integration bundle
- Public event definitions
- Canonical network IDs
- Published checksums
- Public integration repository
- Release artifacts
- Solver-facing ABI
- SDK contract and vectors
- Language SDK sources
- Indexing package
- Onboarding package
- Verification evidence
Reference examples¶
- Discover open routes
- Read the Discovery Facade
- Request an Execution Permit
- Resolve ERC-7683
- Describe an OIF mandate
Documentation discovery¶
robots.txtsitemap.xmlllms.txtllms-full.txt- Local documentation search in the site header
Which source should I use?¶
- Use discovery to find the current public endpoints and expected signer.
- Use the signed Feed for live published route terms.
- Use the permit envelope for one fill's authorized execution.
- Use the on-chain contracts and receipts for state and completion.
- Use SDKs and examples to implement these checks.
- Use Graph/Substreams and documentation for discovery only.
Contributing and support¶
Read the repository contribution guide, start a public design question in Discussions, or report a reproducible defect through Issues.
For security-sensitive reports, follow the repository security policy. You can also send a private documentation ticket.