refactor: update coordinator-api port from 9001 to 8011 and standardize naming
Some checks failed
Cross-Node Transaction Testing / transaction-test (push) Has been cancelled
Deploy to Testnet / deploy-testnet (push) Has been cancelled
Multi-Node Stress Testing / stress-test (push) Has been cancelled
Integration Tests / test-service-integration (push) Has been cancelled
Python Tests / test-python (push) Has been cancelled
API Endpoint Tests / test-api-endpoints (push) Has been cancelled
Production Tests / Production Integration Tests (push) Has been cancelled
Documentation Validation / validate-docs (push) Failing after 14s
Documentation Validation / validate-policies-strict (push) Successful in 4s
Some checks failed
Cross-Node Transaction Testing / transaction-test (push) Has been cancelled
Deploy to Testnet / deploy-testnet (push) Has been cancelled
Multi-Node Stress Testing / stress-test (push) Has been cancelled
Integration Tests / test-service-integration (push) Has been cancelled
Python Tests / test-python (push) Has been cancelled
API Endpoint Tests / test-api-endpoints (push) Has been cancelled
Production Tests / Production Integration Tests (push) Has been cancelled
Documentation Validation / validate-docs (push) Failing after 14s
Documentation Validation / validate-policies-strict (push) Successful in 4s
- Changed all coordinator service port references from 9001 to 8011 in CI workflows - Updated PYTHONPATH references from apps/agent-coordinator to apps/coordinator-api - Renamed log files from agent-coordinator.log to coordinator-api.log - Updated step names and comments to use "coordinator API" instead of "agent coordinator" - Added API versioning documentation explaining /v1 prefix structure for business logic endpoints - Documented CLI compatibility routes (/api/v1) and infrastructure endpoints (no prefix) - Updated architecture
This commit is contained in:
@@ -4,6 +4,18 @@
|
||||
|
||||
FastAPI service that accepts client compute jobs, matches miners, and tracks job lifecycle for the AITBC network.
|
||||
|
||||
## API Versioning
|
||||
|
||||
All business logic endpoints use the `/v1` prefix for consistent versioning. The API structure follows `/v1/{router}/{endpoint}` pattern.
|
||||
|
||||
### Endpoint Structure
|
||||
|
||||
- **Business logic endpoints**: `/v1/{router}/{endpoint}` (e.g., `/v1/marketplace/offers`, `/v1/governance/proposals`)
|
||||
- **CLI compatibility routes**: `/api/v1/{router}/{endpoint}` (e.g., `/api/v1/agents/executions`) - for CLI tools
|
||||
- **Infrastructure endpoints**: No prefix (e.g., `/health`, `/docs`, `/metrics`) - for system operations
|
||||
|
||||
This structure enables future versioning (`/v2`, etc.) while maintaining CLI compatibility and keeping infrastructure endpoints unversioned.
|
||||
|
||||
## Marketplace Extensions
|
||||
|
||||
Stage 2 introduces public marketplace endpoints exposed under `/v1/marketplace`:
|
||||
|
||||
Reference in New Issue
Block a user