Collection of runnable sample servers for local development, integration testing, and demo projects.
| Folder | Purpose | Tech | Default Port |
|---|---|---|---|
| store_server | Store and checkout flow | FastAPI | 8000 |
| payments_server | Payments gateway and store callback | Flask | 5000 |
| file_upload_server | File upload and download API | FastAPI | 8001 |
| search_server | Document indexing and search API | FastAPI | 8002 |
| messaging_server | Room messaging with REST and WebSocket | FastAPI | 8003 |
| otp_auth_server | OTP auth and session token flow | FastAPI | 8004 |
Run each server in its own terminal.
cd store_server
pip install -r requirements.txt
python -m uvicorn main:app --reload --port 8000cd payments_server
pip install -r requirements.txt
python main.pycd file_upload_server
pip install -r requirements.txt
python -m uvicorn main:app --reload --port 8001cd search_server
pip install -r requirements.txt
python -m uvicorn main:app --reload --port 8002cd messaging_server
pip install -r requirements.txt
python -m uvicorn main:app --reload --port 8003cd otp_auth_server
pip install -r requirements.txt
python -m uvicorn main:app --reload --port 8004Each server includes a SKILL.md file that documents:
- Core workflows and use cases
- Endpoint details and error patterns
- Integration points with other services
- Common scenarios and edge cases
For agents and developers: You can reference or feed a server's SKILL.md file to your agent to give it domain knowledge about that API. This enables faster and more accurate integration without manual API exploration.
Example for your agent:
Here is the skill file for the store server:
<contents of store_server/SKILL.md>
- Each project uses main.py as the entrypoint.
- Each project includes a local requirements.txt.
- Each project includes a SKILL.md file for agent/developer reference.
- FastAPI services expose interactive docs at /docs.
- Data is in-memory by default and resets on restart.
- Create a cart in the store server.
- Add items and checkout to get order_id and total.
- Call payments server endpoint POST /payments/orders.
- Payments server confirms to store via POST /payments/confirm.
- Store updates order status to paid or payment_failed.
Legacy payments route POST /pay/order is still available for compatibility.