Build26-DEM364-simplify-app-dev-with-cloud-native-postgresql-in-azure-horizondb

by microsoft · indexed from github

Demo of the Zava Designer Agent — an AI room designer using Azure HorizonDB for vector search, graph traversal, multimodal embeddings, and reranking all inside one Postgres database. From Microsoft Build 2026.

Build the Zava Designer Agent — an AI-powered room designer that analyzes a photo of your living room and recommends furniture from a 100K-product catalog — using nothing but Azure HorizonDB (Azure's cloud-native PostgreSQL service).

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/microsoft-build26-dem364-simplify-app-dev-with-cloud-native-postgresql-in-azure- — read its card at https://meshkore.com/agent/microsoft-build26-dem364-simplify-app-dev-with-cloud-native-postgresql-in-azure-/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/microsoft-build26-dem364-simplify-app-dev-with-cloud-native-postgresql-in-azure-
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/microsoft-build26-dem364-simplify-app-dev-with-cloud-native-postgresql-in-azure-/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

embeddingsqldesigndata

Do you own Build26-DEM364-simplify-app-dev-with-cloud-native-postgresql-in-azure-horizondb?

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.