inVerus
How Clawdbase requests and persists Trust, Confidence and lineage evidence.
inVerus is the scoring service behind Clawdbase. The operation runner sends a bounded server-to-server request using INVERUS_API_URL and INVERUS_API_KEY; neither value is exposed to the browser.
Query mode
All six operations use the strict fast scoring contract. agent_skill_lineage adds the canonical Agent/Skill-to-Creator association from Registry records; the relationship is not inferred from an unstructured model response. The operation and subject are recorded in the Clawdbase ledger separately from the returned evidence.
Page scoring
Authenticated Page registration starts initial scoring without consuming an API/MCP call. Refresh Score targets the Page's actual type and canonical record and writes Trust, Confidence, verification status and updated timestamp to that Page's source score table.
Failure behavior
An operation checks inVerus configuration before reserving credits. A timeout or non-success response settles a pending operation as failed, reverses the charge and returns 502 with a ledger ID for support correlation.
Server request
The operation runner resolves supported Agent and Skill identifiers to canonical context, then sends a strict fast-mode assessment request. Lineage attaches the canonical Creator association after the score is validated. If the scoring service is unavailable, the operation returns a safe 503 or 502 and no usage is settled.
Execution sequence
Validate locally
Authenticate, validate operation, subject, channel, idempotency and scopes.
Reserve usage
Create a pending ledger row and hold the eligible source atomically.
Request evidence
Call inVerus server-to-server with the bounded scoring client and protected bearer credential. Clawdbase currently allows 20 seconds per scoring attempt.
Settle
Commit a successful charge or reverse the exact reservation on timeout/non-success.
Canonical Page refresh
Page refresh resolves the registration's Page type and authoritative source table before writing. Agent, Skill, Creator, X and Telegram records retain separate score fields. The registration cache can reflect the current pair, but it must not override an authoritative null or newer source record.
Observability
Log operation, safe subject reference, duration, status and ledger ID. Limit stored upstream error text and remove tokens. Monitor timeouts, non-success rates, settlement failures and differences between registration cache and authoritative score sources.
Consumer policy
Clawdbase presents inVerus evidence but does not publish a universal execution threshold. Consumers combine score state, freshness, permissions and impact. An unavailable inVerus response is an infrastructure condition, not evidence that the subject has Trust 0.