py-agent-ner
NER training-data generation built on py-agent-lib. Bring your own labels, LLM, and downstream trainer.
Architecture: one LLM call per (text, label). Each call uses a single-value Literal[" "] enum on its response schema; the model returns the verbatim substrings it found for that label. You fan out N calls per text (asyncio or DagExecutor) and assemble a TrainingRecord from the N responses. The package gives you the shapes, the prompt template, the schema builder, and the BIO converter — nothing else. The loop, the fan-out, and the merge are in your code where you can see them.
⚡ 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/vector-py-agent-ner — read its card at https://meshkore.com/agent/vector-py-agent-ner/.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.
https://meshkore.com/agent/vector-py-agent-nerFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/vector-py-agent-ner/.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
Do you own py-agent-ner?
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.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.