Skip to content
Back to search

opensemanticagent

Open Semantic Agent (OSA): an open spec for pub/sub that routes messages by meaning, under AI budgets.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/opensemanticagent--opensemanticagent/badge.svg)](/listings/opensemanticagent--opensemanticagent)

HTML

<a href="/listings/opensemanticagent--opensemanticagent"><img src="/api/listings/opensemanticagent--opensemanticagent/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 59 lines
  1. # Open Semantic Agent (OSA)
  2. [![OpenSSF Best Practices](https://www.bestpractices.dev/projects/16976/badge)](https://www.bestpractices.dev/projects/16976) [![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.24417032.svg)](https://doi.org/10.5281/zenodo.24417032) [![PyPI](https://img.shields.io/pypi/v/open-semantic-agent)](https://pypi.org/project/open-semantic-agent/) [![License](https://img.shields.io/badge/license-Apache--2.0-blue)](LICENSE)
  3. **An open spec for publish/subscribe that routes messages by what they mean.**
  4. Website: **https://opensemanticagent.org** · Spec: [`spec/SPEC.md`](spec/SPEC.md)
  5. OSA sits on top of the message transport you already run (Kafka, NATS, Redis Streams, SQS) and works with whichever model you choose. Each message goes through three checks in order: a free topic match, a cheap similarity check, and an AI judge only when the first two are unsure, under token budgets. Every decision is audited and replayable.
  6. | Conventional broker | Open Semantic Agent |
  7. |---|---|
  8. | String topics | Semantic subscriptions: subscribe by meaning |
  9. | Payload delivered as-is | Schema mediation: each subscriber gets its own contract |
  10. | Dedupe by message ID | Semantic dedupe: 40 alerts about one incident become 1 |
  11. | Static priority | Reasoned urgency, with a recorded rationale |
  12. | Slow consumer → lag or drop | Backlog summarization: a digest instead of a loss |
  13. | Dead-letter queue | Self-healing DLQ: diagnose, repair, retry or escalate |
  14. | Replay the raw log | Briefings: "catch me up on order 123 since Monday" |
  15. | One reply | Consensus fan-in: ask N agents, reconcile the answers |
  16. | Per-topic ACLs | Per-subscriber redaction by clearance |
  17. | Opaque routing | Every decision audited and replayable |
  18. ## Use it from an AI assistant
  19. The spec ships as a small MCP server, so any MCP client (Claude, Cursor, VS Code and others) can read it and check documents against it:
  20. ```bash
  21. uvx open-semantic-agent # or: pip install open-semantic-agent
  22. ```
  23. Tools, all read-only: `osa_list_sections`, `osa_get_section`, `osa_search_spec`, `osa_get_schema`, `osa_validate` (envelope, subscription manifest, audit record, stream message), `osa_list_fixtures`, `osa_get_fixture`. It is listed in the MCP Registry as `io.github.opensemanticagent/opensemanticagent`.
  24. <!-- mcp-name: io.github.opensemanticagent/opensemanticagent -->
  25. ## What's here
  26. | Path | What it is |
  27. |---|---|
  28. | `spec/SPEC.md` | The specification (0.2, draft) |
  29. | `schemas/` | JSON Schemas for the envelope, subscription manifest, audit record and stream messages. Each `$id` resolves on the website. |
  30. | `conformance/fixtures/` | Routing test vectors that implementations run against |
  31. | `osa/`, `tests/` | The MCP server and its tests. The package bundles the spec, schemas and fixtures. |
  32. | `tools/build_site.py`, `docs/` | The website. `pip install markdown && python3 tools/build_site.py` rebuilds `docs/`, which GitHub Pages serves. |
  33. ## Implementations
  34. Building one? Open an issue and we'll list it here.
  35. ## Contributing
  36. See [CONTRIBUTING.md](CONTRIBUTING.md). Spec changes go through a pull request against `spec/SPEC.md`; changes that affect routing add or update fixtures in `conformance/fixtures/`. Questions and ideas go to [Discussions](https://github.com/opensemanticagent/opensemanticagent/discussions). Security issues: see [SECURITY.md](SECURITY.md).
  37. If you cite the spec, use [CITATION.cff](CITATION.cff) or DOI [10.5281/zenodo.24417032](https://doi.org/10.5281/zenodo.24417032) (all versions).
  38. ## License
  39. Apache-2.0.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.