Current HTTP routes used by Tenzarch developer integrations.
This reference preserves verified route names already used by the current product. It does not invent undocumented request fields or response schemas simply to make the reference look larger.
Developer profile and key management.
Routes
POST /api/developers
GET /api/developers/me
POST /api/developers/keys
GET /api/developers/keys
DELETE /api/developers/keys/:keyId
POST /api/developers/keys/:keyId/rotateDiscovery and submission.
Routes
GET /api/marketplace/services
POST /api/marketplace/services/:id/executeExecution inspection.
Routes
GET /api/developers/jobs
GET /api/developers/jobs/:jobId
GET /api/developers/jobs/:jobId/logs
GET /api/developers/jobs/:jobId/telemetryUsage-account inspection.
Routes
GET /api/credits/balance
GET /api/credits/historyOnly verified backend contracts belong in reference documentation.
Route names above are preserved from the current system. Exact bodies, fields, scopes, status codes, limits, and validation rules should be documented when confirmed from the backend implementation. The documentation should never fabricate technical precision.
