How it works
Edge sits between connected sources and your agent. It applies your access and spending rules before content enters, then records what happened.
Read the source’s terms
Edge checks robots rules, content signals and licence files before requesting a web page.
Apply your rules
Source access, licences, spending limits and content checks determine what reaches the agent.
Keep a source record
Record the source, terms, available cost, content fingerprint and decision, with any gaps in the evidence.
Compare results
Run the same task and model with different sources. Compare how well each answer is supported, what it covers, freshness and cost.
Your retrieval and memory stack
Keep your RAG, vector database or memory service in charge of ingestion, indexing and retrieval. Connect it through asource adapterto apply Common Measure’s rules to the content it returns.
Build your own extensions.
Add security and privacy checks, tools that select or condense content, checks that answers stay true to their sources, or records of how an output was produced. Each time an extension runs, the record names it and shows its configuration and result.
Keep in-house extensions in your private catalogue or choose specialist tools from the extension marketplace. Approve each extension version for your organisation through Hub.
Developers use the same public extension contractfor custom and marketplace extensions.
Which reads can be blocked?
Reads through context_fetch or context_searchcan be refused before content reaches the agent. Hooks record supported activity afterwards; they cannot block it. With the Claude Code plugin on Claude Code 2.1.287 or later, Claude Code’s own WebFetch and WebSearch go through Common Measure too. Other built-in tools remain outside Common Measure’s control. Imported history records past activity without authorising it to be shared.
Technical specification
- Hosts
- Registration routes and session evidence for local agent hosts
- Integration
- Hooks and MCP tools:
context_fetch,context_search,context_status - Evidence grades
- Mediated, observed, reconstructed; never merged
- Hashing
- SHA-256 over RFC 8785 canonical JSON
- Identity
- Enrolled edges sign requests with RFC 9421 HTTP message signatures under Web Bot Auth; unenrolled edges report unsigned requests
- Reporting
- Content Telemetry v1.0, to a receiver the operator names
- Runs
- On each person's machine; local policy and records work offline. Live acquisition needs its sources; Common Measure Hub is optional.
Access, payment and terms by source
Access, payment and terms by source
| Source | Access | Payment | Terms |
|---|---|---|---|
| Web search APIs | API key | Per query, prepaid credits | Provider terms of service |
| Grounding services | API key or cloud account | Per request | Provider terms of service |
| Data markets and licensed feeds | Contract or OAuth | Subscription, wallet or per item | A licence per publisher |
| The open web | None, or a signed bot identity | Free, or pay per crawl | robots.txt, licence files, site terms |
| Code repositories and packages | Access token | Free, or per seat | A licence per project |
| MCP servers and skills | Configuration per server | Varies | Often unstated |
| Internal documents | Single sign-on and permissions | None | Confidentiality and client rules |
| Common Measure | Connected agent tools | Budget checks before Edge sends a request | Your source rules applied to reads through Edge |
Common Measure Hub
Common Measure Hub lets your team share a source policy and review approved records together. Edge applies the policy locally and keeps the last accepted policy when Hub is unavailable.
You choose which directories may report. Prompts, answers, document text and internal reads stay local. See what is shared.
Hub access is by invitation during the pilot, which is free, including invited colleagues. Join the waiting list.
Invited by a colleague? Join your organisation. Admitted? Set up your organisation.