Reference
Technical reference material that doesn't belong in workflow-oriented pages.
This section should stay exact, short, and non-narrative.
Use Reference when you need:
- exact terminology
- endpoint ownership
- error meanings
- route history
Do not start here if your goal is to:
- integrate a package
- understand a workflow
- learn the product surface
In those cases, start in the owner sections first and come back here only for precise facts.
API Reference
Endpoint tables for api.dexter.cash and x402.dexter.cash.
Facilitator Error Codes
Policy and backpressure error codes returned by the facilitator.
Glossary
Shared terminology used across the docs.
Legacy Routes
Where old doc URLs map to in the current structure.
Quick Routing
- Need exact endpoint ownership? Go to API Reference.
- Need terminology clarity? Go to Glossary.
- Need facilitator error meanings? Go to Facilitator Error Codes.
- Need old-path cleanup? Go to Legacy Routes.