Trust
Methodology
What ABATODA states, how it knows, and what it refuses to guess. Every claim carries its own status; providers as a whole are never labelled verified.
Evidence states
Checked by an ABATODA verification run with recorded run id, time and verifier.
Backed by a cited source (docs, pricing page, auditor) but not re-checked by ABATODA.
Derived by ABATODA logic from other evidence. Never shown as a fact.
Asserted (e.g. by the vendor) with no independent check.
Two or more sources disagree. Both are shown.
Evidence exists but is older than the freshness window.
No acceptable evidence. Displayed as UNKNOWN, never estimated.
Verification runs
Live verification runs are performed and stored with method, time, outcome and hash. Vendor documentation alone is never enough for VERIFIED.
source_refresh / docs_crawl
Fetches an official source server-side, records fetched_at, content hash and baseline/changed outcome. Extracted statements become candidate claims (UNVERIFIED) — never VERIFIED.
pricing_refresh
Re-fetches an official pricing page. Prices stay SUPPORTED because they are vendor-published.
endpoint_probe
Safe, unauthenticated request to a documented endpoint. Only the narrow observed fact (e.g. reachable, requires sign-in) can become VERIFIED.
Claim review
Candidate claims are triaged by an auditable ruleset (abatoda:triage_rules_v1) that only suggests. An owner or admin may accept a suggestion as SUPPORTED with rule codes recorded, mark it CONFLICTING, or reject it. Manual review can never produce VERIFIED.
Freshness windows
- Pricing
- 7 days
- API / integration
- 30 days
- Security / compliance
- 90 days
- General metadata
- 180 days
Older evidence is shown as STALE. Source update dates are never invented; if a source does not state one, it is UNKNOWN.
Sponsorship separation
Ordering uses fit score, then freshness. Payment, referral revenue and listing fees are excluded inputs and are listed under excluded_inputs in machine output. Any commercial relationship is disclosed next to the provider.
Live and demo data
Results come from the live catalog. Labelled demo fixtures exist only behind an explicit opt-in and are never mixed into a live result. When the live catalog has no coverage, the answer is UNKNOWN.
What ABATODA is not
Not an app directory, API marketplace, review site, workflow automation platform or execution runtime. Postman, Zapier, Pipedream, Composio, official SDKs and official MCP servers are treated as downstream routes.