One API call.
Verified trust signals.
Query the Mediary protocol to get structured, verified trust data about any claimed entity. No scraping, no inference, no guesswork.
Mediary provides a REST API at api.mediary.co/api/v1 that returns structured trust profiles for verified businesses. Each profile includes a TRI score from 0 to 100, individual signal statuses for 8 verified signals, and verification timestamps β all in machine-readable JSON with no authentication required. See the developer integration guide for setup details, or check pricing for API rate limits and tiers.
Why integrate instead of scraping?
You could scrape trust signals yourself. But scraped data is noisy, unstructured, and expensive to maintain. Mediary gives you verified, structured, queryable data with zero maintenance.
| Mediary API | Scrape it yourself | Custom heuristics | |
|---|---|---|---|
| Data quality | Verified | Noisy | Variable |
| Maintenance | Zero | High | High |
| Structured output | JSON, typed | HTML parsing | Custom format |
| Cost per query | Free (rate limited) | Compute + bandwidth | Varies |
Try it now
Query a demo trust profile. No API key needed.
# Get a trust profile
curl https://api.mediary.co/api/v1/entities/demo/trust.json
Returns JSON with TRI score, individual signal statuses, verification timestamps, and confidence level. No authentication required for read access.
Canonical Endpoint
GET
/api/v1/entities/{entity_id}/trust.json
Returns the complete trust profile for an evaluated entity. No authentication required for public profiles.
Response Schema
{
"schema_version": "tri-v0",
"entity": {
"id": "uuid",
"domain": "example.com",
"name": "Example Business Ltd"
},
"tri": {
"score": 72, // 0-100 composite
"mtr": 68, // machine trust readiness
"htr": 76, // human trust readiness
"confidence": 0.85 // signal coverage
},
"signals": [
{
"key": "website_reachable",
"value": true,
"weight": 10,
"layer": "mtr",
"verified_at": "2026-03-24T10:00:00Z"
}
// ... 7 more signals
],
"computed_at": "2026-03-24T10:00:00Z"
} Discovery Mechanisms
HTML Link Relation
Well-Known Endpoint
Direct API Query
Agent Decision Pattern
# Pseudocode: agent evaluating a business
profile = fetch("https://api.mediary.co/entities/{id}/trust.json")
# Check minimum trust threshold
if profile.tri.score >= 60 and profile.tri.confidence >= 0.7:
# Business meets trust threshold
include_in_recommendations(profile.entity)
else:
# Insufficient trust signals
skip_or_flag(profile.entity) Agents set their own thresholds. Mediary provides the data; the agent makes the decision.
Open Protocol
Mediary is an open protocol, not a walled garden. The trust profile schema is versioned and publicly documented. Any agent can query it. Any business can claim their profile.
- No API key required for reading public profiles
- Schema versioned (tri-v0) β breaking changes increment version
- Signal registry is immutable within a protocol version
- TRI calculation is deterministic β same signals, same score
Versioning and stability
The trust profile schema is versioned. Within a protocol version, the signal registry and TRI calculation are immutable.
tri-v0. Incremented on breaking changes.Rate limits and access
Cache-Control headers. Profiles update at most once per hour.Frequently Asked Questions
- Do I need an API key?
- No. Read access to trust profiles is free and requires no authentication. Rate limits apply to prevent abuse. Write access (for claiming and verifying domains) will require authentication when available.
- What format does the API return?
- JSON. Each response includes a TRI score (0-100), individual signal statuses (verified/unverified/pending), verification timestamps, and a confidence percentage. The schema is documented and versioned.
- How fresh is the data?
- Trust signals are re-verified periodically. The API response includes verification timestamps for each signal so you can assess freshness. Profiles update automatically β no manual refresh needed.