repositories
loading repo index
repositories
loading repo index
repository
loading code, commits, and activity
public Clawd ADK gateway launch mirror
stars
latest
clone command
git clone gitlawb://did:key:z6Mkq5mY...iFZ5/my-project-publ...git clone gitlawb://did:key:z6Mkq5mY.../my-project-publ...2fa351d6docs: add automaton and perps launch sources15d ago| #1 | <div align="center"> |
| #2 | |
| #3 | <img src="https://capsule-render.vercel.app/api?type=waving&color=0:05060d,20:174ea6,45:4285F4,70:34A853,100:05060d&height=230§ion=header&text=OpenClawd%20Google%20ADK&fontSize=44&fontColor=ffffff&animation=twinkling&fontAlignY=38&desc=Private%20registry%20tools%20for%20governed%20agent%20routing&descAlignY=60&descSize=16" alt="OpenClawd Google ADK" /> |
| #4 | |
| #5 | <br/> |
| #6 | |
| #7 | <img src="https://readme-typing-svg.demolab.com?font=JetBrains+Mono&weight=900&size=18&duration=1700&pause=350&color=34A853¢er=true&vCenter=true&width=900&lines=ADK+LlmAgent+%2B+FunctionTools;private+destinations+%2B+registry+coverage;135+installed+catalog+agents+discoverable;unsigned+swap+prep+only+%E2%80%94+wallet+signing+stays+outside+the+model" alt="ADK capabilities" /> |
| #8 | |
| #9 | </div> |
| #10 | |
| #11 | --- |
| #12 | |
| #13 | # OpenClawd Google ADK Agent |
| #14 | |
| #15 | This is the private TypeScript ADK entrypoint for the OpenClawd registry and agent catalog. It exports `rootAgent` from [`agent.ts`](./agent.ts), following the ADK TypeScript `LlmAgent` + `FunctionTool` pattern. |
| #16 | |
| #17 | ## What It Connects |
| #18 | |
| #19 | | Surface | Status | |
| #20 | | --- | --- | |
| #21 | | Google ADK TypeScript | `@google/adk` `LlmAgent` entrypoint | |
| #22 | | Clawd agent catalog | Reads `agents/agents-catalog.json` | |
| #23 | | Installed agent registry | Reads all `agents/src/*.json` source-backed agents | |
| #24 | | Private destinations | Publishes the nine x402.wtf gateway/catalog destinations | |
| #25 | | Solana market data | Uses Jupiter read endpoints | |
| #26 | | Swaps | Prepares unsigned Jupiter swap payloads only | |
| #27 | |
| #28 | The gateway-side manifest is available at: |
| #29 | |
| #30 | ```text |
| #31 | GET /adk/manifest.json |
| #32 | ``` |
| #33 | |
| #34 | It reports private mode, destination URLs, catalog counts, and any source/catalog mismatches. |
| #35 | |
| #36 | ## Run |
| #37 | |
| #38 | ```bash |
| #39 | cd adk |
| #40 | npm run check |
| #41 | npm run run |
| #42 | ``` |
| #43 | |
| #44 | For the ADK dev UI: |
| #45 | |
| #46 | ```bash |
| #47 | cd adk |
| #48 | npm run web |
| #49 | ``` |
| #50 | |
| #51 | For a local Express API server: |
| #52 | |
| #53 | ```bash |
| #54 | cd adk |
| #55 | npm run api |
| #56 | ``` |
| #57 | |
| #58 | ## Private Wiring |
| #59 | |
| #60 | The agent exports `rootAgent` from `agent.ts` and uses multiple ADK `FunctionTool`s for: |
| #61 | |
| #62 | - agent catalog and registry coverage |
| #63 | - private destination discovery |
| #64 | - token search and price lookup |
| #65 | - unsigned Jupiter swap preparation for wallet review |
| #66 | |
| #67 | Real secrets belong in `adk/.env` or the shell. Do not commit RPC URLs, API keys, wallet keys, or bot tokens. |
| #68 | |
| #69 | Use [`adk/.env.example`](./.env.example) as the non-secret template. |
| #70 | |
| #71 | ## Gateway Contract |
| #72 | |
| #73 | The ADK agent is designed to sit behind the private gateway documented in [`../gateway/README.md`](../gateway/README.md). |
| #74 | |
| #75 | | ADK tool | Gateway policy intent | |
| #76 | | --- | --- | |
| #77 | | `get_agent_catalog_stats` | safe read-only registry coverage check | |
| #78 | | `search_agent_catalog` | safe read-only discovery over installed agents | |
| #79 | | `get_private_destinations` | controlled disclosure of governed destination labels and URLs | |
| #80 | | `get_token_price` | public market metadata lookup | |
| #81 | | `get_token_search` | public token metadata lookup | |
| #82 | | `prepare_jupiter_swap` | unsigned transaction preparation only; wallet signing stays outside the model | |
| #83 | |
| #84 | Production deployments should restrict MCP `tools/call` to the exact tool names required for the workflow and should route sensitive traffic through IAP, Model Armor, or a custom authorization extension before it reaches private destinations. |
| #85 |