Seeed-Jetson-DevelopTool / gapi-setup
CLAUDE.md57 starsChanged 4 months agoMITView on GitHub
Deploy Gapi embeddable API gateway on Jetson Orin for streaming AI micro service integrations. Covers Docker-based installation, workflow engine setup, and community micro services. Requires any Jetson Orin with Docker and 1.3GB storage.
- Pipes a download into a shell
In this repository297 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-nvrAGENTS.md
- allxon-ota-updateAGENTS.md
- allxon-setupAGENTS.md
- alwaysai-setupAGENTS.md
- backup-restoreAGENTS.md
- bsp-source-buildAGENTS.md
- clawdbot-developmentAGENTS.md
- cochl-sense-setupAGENTS.md
- cvedia-setupAGENTS.md
- dashcamnet-xavier-nx-multicameraAGENTS.md
- deciai-setupAGENTS.md
- deepseek-quick-deployAGENTS.md
- deploy-deepseek-mlcAGENTS.md
- deploy-depth-anything-v3AGENTS.md
- deploy-diaAGENTS.md
- deploy-efficient-vision-engineAGENTS.md
- deploy-frigateAGENTS.md
- deploy-live-vlm-webuiAGENTS.md
- deploy-nvbloxAGENTS.md
- deploy-ollama-anythingllmAGENTS.md
- deploy-riva-llama2AGENTS.md
- developtool-deviceAGENTS.md
- disk-encryptionAGENTS.md
- diy-bsp-buildAGENTS.md
- ethercat-communicationAGENTS.md
- ethercat-setupAGENTS.md
- finetune-llm-llama-factoryAGENTS.md
- fix-browser-snap-jetsonAGENTS.md
- gapi-setupAGENTS.md
- generative-ai-introAGENTS.md
- gpt-oss-liveAGENTS.md
- gr00t-n1-5-deploy-thorAGENTS.md
- gr00t-n1-6-deploy-agxAGENTS.md
- hardhat-setupAGENTS.md
- hybrid-bsp-dk-to-recomputerAGENTS.md
- imx477-a603-setupAGENTS.md
- j501-viola-fruit-sortingAGENTS.md
- jetpack5-ssd-boot-fixAGENTS.md
- jetpack-flash-wsl2AGENTS.md
- jetpack-jetson-overviewAGENTS.md
- jetpack-ota-updateAGENTS.md
- jetson-ai-toolsAGENTS.md
- jetson-docker-setupAGENTS.md
- jetson-faqAGENTS.md
- jetson-pc-wired-shareAGENTS.md
- jetson-project-galleryAGENTS.md
- jetson-resource-indexAGENTS.md
- jetson-tutorial-exercisesAGENTS.md
- ko-module-buildAGENTS.md
- l4t-differencesAGENTS.md
- langchain-output-formattingAGENTS.md
- lerobot-env-setupAGENTS.md
- llama-cpp-rpc-distributedAGENTS.md
- llm-interface-controlAGENTS.md
- local-chatbot-multimodalAGENTS.md
- local-chatbot-physicalAGENTS.md
- local-llm-text-to-imageAGENTS.md
- local-rag-llamaindexAGENTS.md
- lumeo-setupAGENTS.md
- The first 60 shown.
The file
We split this CLAUDE.md into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Run one phase at a time. After each phase:
- Very specific: line 14
If output contains [STOP] → stop immediately, consult the failure decision tree below.
- Very specific: line 15
If output ends with [OK] → tell the user "Phase N complete" and proceed to the next phase.
- Distinctive: line 39
Verify the container is running:
- Distinctive: line 73
Follow the instructions in the blue box to download your custom configuration
- Distinctive: line 74
Follow the per-service install instructions below that
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Getting Started with Gapi on Jetson
Execution model
Run one phase at a time. After each phase:
- Relay all command output to the user.
- If output contains
[STOP]→ stop immediately, consult the failure decision tree below. - If output ends with
[OK]→ tell the user "Phase N complete" and proceed to the next phase.
Prerequisites
| Requirement | Details |
| Hardware | Any NVIDIA Jetson Orin |
| Software | Docker installed and running |
| Storage | ≥1.3 GB for Gapi server |
| Network | Required for Docker pull and web access |
Phase 1 — Install Gapi server (~5 min)
mkdir ~/gapiData && cd ~/gapiData
curl -L https://raw.githubusercontent.com/genai-nerds/Gapi/main/gapiConfigs.zip -o gapiConfigs.zip
unzip -q gapiConfigs.zip
docker run -d --name gapi --network host -v ~/gapiData:/opt/gapi/vdata genainerds/gapi:arm64 /bin/bash -c "cd /opt/gapi/bin && ./startGapi.sh"Verify the container is running:
docker ps | grep gapi[OK] when the gapi container is listed as running. [STOP] if Docker pull or container start fails.
Phase 2 — Log in to Gapi WebUI (~1 min)
Open a browser and navigate to:
http://<jetson-ip>:8090Default credentials:
- User:
root - Password:
!gapi2024
Change the password in Settings after first login. SSL cert setup is covered in the Gapi docs.
[OK] when you can log in and see the Gapi dashboard.
Phase 3 — Explore workflows and micro services
Workflows visually connect Nodes that talk to Micro Services and APIs. Each Node can append or reference rolling Transaction data.
To set up Community Micro Services:
- Go to the Micro Services tab in the Gapi UI
- Follow the instructions in the blue box to download your custom configuration
- Follow the per-service install instructions below that
Community Micro Service storage requirements: ~4 GB to ~10 GB each.
[OK] when at least one micro service is connected and visible in the UI.
For workflow tips, micro service architecture details, and custom on_message handlers, see
references/source.body.md.
Failure decision tree
| Symptom | Action |
docker: command not found | Install Docker: curl https://get.docker.com | sh && sudo systemctl enable --now docker |
| Docker pull fails | Check internet connectivity. Verify Docker daemon is running with sudo systemctl status docker. |
| Container exits immediately | Check logs: docker logs gapi. Ensure ~/gapiData contains the unzipped config files. |
| Cannot access port 8090 | Verify container is running with docker ps. Check firewall. Try http://localhost:8090 from the Jetson itself. |
| Login fails | Use default credentials root / !gapi2024. Clear browser cache if needed. |
| Micro service won't connect | Ensure the micro service container has network access. Check the streaming websocket connection in logs. |
Reference files
references/source.body.md— full original Seeed tutorial with workflow diagrams, micro service architecture, and integration details (reference only)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

