# Limitations

- xMESH is specialized for constrained x402 service routing.
- The model needs a current candidate set supplied by a trusted retriever.
- Deterministic code must enforce budgets, networks, approvals, schemas, endpoint identity, replay protection, and settlement recovery.
- The model does not hold wallets or execute requests.
- The validated context contract is 2,048 tokens.
- CPU inference favors portability over latency; optimized GPU and native runtimes should be used for production throughput.