Data Egress
Create consumption APIs to serve your data
This demo will walk you through using Aurora tools to prompt your way to creating consumption APIs that serve the aircraft telemetry data you’ve ingested.
Skip to prompt if you started with the ads-b template.
Prerequisites
- Aurora and Moose CLIs: Install them here
- OS: macOS or Linux (WSL supported for Windows)
- Docker Desktop/Engine: 24.0.0+
- Node: version 20+ (LTS recommended)
- Anthropic API Key: Get one here
- Client: Cursor
- Completed: Ingest Demo (or have data already in your system)
Start with the ads-b template
Terminal
aurora init egress-demo ads-bTerminal
cd egress-demo
npm installRun the Moose Dev Server
Terminal
moose dev Open the project in Cursor
Initialize the Aurora MCP
Navigate to Cursor > Settings > Cursor Settings > Tools and Integrations then toggle on the Aurora MCP tool.
For best results, set the LLM to claude-4-sonnet
Gemini 2.5 and o3 are also reasonably good, but claude-4-sonnet has the most consistent results.
Prompt the LLM to create a geolocation API
Can you create an API that returns every aircraft within X miles of Y,Z coordinates.
Action
The LLM should now use aurora tools to:
- create the consumption API endpoint that calculates distance and filters aircraft
- test the API to ensure it’s working correctly with the existing aircraft data
You’ll know it is succeeding if:
- the LLM successfully tests the API
- you can curl the API generated
- you can see the generated openapi spec in
path/to/your/project/.moose/openapi.yaml