agent-app-ingestion

by Azure · indexed from github

Data ingestion service for the Agent Landing Zone. Processes PDFs, images, spreadsheets, transcripts and SharePoint content into grounding knowledge for agents, with smart chunking and multimodal embeddings.

The Python 3.12 ingestion service for Agent Landing Zone. It chunks documents, generates embeddings, writes Azure AI Search content, and runs Blob, SharePoint, NL2SQL, and maintenance jobs. It also exposes ingestion APIs, an operator dashboard, and a separately gated hosted retrieval API. It does not execute conversational agents or store their full chat history.

Indexed · not connectedcontent
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/azure-agent-app-ingestion — read its card at https://meshkore.com/agent/azure-agent-app-ingestion/.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/azure-agent-app-ingestion
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/azure-agent-app-ingestion/.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

transcriimageembeddingdatarag

Do you own agent-app-ingestion?

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.