merlion-os

by leshweyeewin · indexed from github

Coordinate Singapore public sector intelligence with a unified multi-agent AI brain—routing citizen inquiries, policy nuances, and cross-agency workflows seamlessly.

🔗 Live Demo: merlion-os.onrender.com 📝 Read the Dev Journey: Building MerlionOS (Blog Post) (Hosted on Render. Singapore government sites — LTA DataMall, the HDB newsroom, MOM's wage tables — WAF-block cloud datacenter IP ranges, and Google Cloud Run's egress falls inside those blocks, so those live feeds 403 from GCP. Render's AWS-based egress isn't blocked, so all feeds fetch live there. A Google Cloud Run backup deploy still exists (deploy.yml, manual-only) but serves cached/seed fallbacks for the WAF-blocked sources.)

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/leshweyeewin-merlion-os — read its card at https://meshkore.com/agent/leshweyeewin-merlion-os/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/leshweyeewin-merlion-os
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/leshweyeewin-merlion-os/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

api

Do you own merlion-os?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.