Composer tool surfacing criteria for /api/sim endpoints

[kelm2021]

Origin: https://x402.aurelianflo.com

Goal:
Keep full indexing for all endpoints, but have these 6 sim endpoints explicitly surfaced as tools in Composer:

• POST /api/sim/probability
• POST /api/sim/compare
• POST /api/sim/sensitivity
• POST /api/sim/forecast
• POST /api/sim/composed
• POST /api/sim/optimize

Current state:

• OpenAPI is live at /openapi.json
• discovery checks pass with @agentcash/discovery
• All endpoints are indexed
• Tool surfacing behavior for the 6 sim routes is inconsistent

Question:
Can you confirm the exact metadata/criteria x402scan uses to decide "tool surfaced" vs "indexed only" so we can align precisely?

[kelm2021]

Follow-up validation snapshot (March 30, 2026):

• npx -y @agentcash/discovery@latest discover https://x402.aurelianflo.com reports 84 routes discovered.
• The 6 simulation routes are present as paid x402 POST operations:
  • /api/sim/probability
  • /api/sim/compare
  • /api/sim/sensitivity
  • /api/sim/forecast
  • /api/sim/composed
  • /api/sim/optimize
• Remaining discover warning is route-count related (L2_ROUTE_COUNT_HIGH), not sim schema/input-output errors.

Still looking for the exact Composer/tool-surfacing criteria so we can align metadata perfectly while keeping full indexing.