GlossoGen

by agencyenterprise · indexed from github

A platform for running controlled experiments on teams of LLM agents: multi-agent simulations, an event-sourced run log, swap and fork interventions, and post-hoc evaluation metrics.

A platform for studying how LLM agents communicate when they have to. Agents are put in a simulated task where no single one of them holds enough information to succeed, so nothing gets solved without talking. In most scenarios every character they send then costs against a fixed per-round budget, and under that pressure they compress, abbreviate, and invent shorthand. The platform records all of it and scores it afterwards.

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

apiresearchllm

Do you own GlossoGen?

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.