Agent Pages
Evaluate a registered or discovered Agent before delegation or execution.
Agent Pages center the Agent Trust and Confidence pair, source repository, Creator context and available lineage.
Check before use
- Confirm that the Page refers to the expected owner and repository.
- Read Trust and Confidence with the last-scored timestamp.
- Open Creator and lineage context when available.
- Review the Agent's requested permissions and deployment boundary separately.
The programmable operation is agent_score, priced at 10 credits for paid-credit accounting. Free calls consume one monthly call rather than the displayed credit amount.
Route and identity
Agent Pages are available by readable repository route and immutable ID route:
/a/{owner}/{repo}
/a/id/{id}Use the ID form when a stable internal reference matters. Use the owner/repository form for human navigation. A repository rename may change the readable route without creating a new canonical Agent.
Page anatomy
An Agent Page should expose the Agent identity, source repository, verification state, Trust and Confidence, last-scored time, Creator relationship and available lineage. Editable summary or presentation fields are visually separated from these system facts.
Programmatic refresh
For a decision-time assessment, call the operation runner from a server environment:
curl --request POST 'https://www.clawdbase.ai/api/clawdbase/operations/run' \
--header "Authorization: Bearer $CLAWDBASE_API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"operation":"agent_score",
"subject":"owner/repository",
"channel":"api",
"idempotency_key":"agent-owner-repository-01"
}'An external operation is metered and returns its own inVerus result. The Console Refresh Score action updates the canonical Page through the Page refresh route. Do not assume those workflows have the same billing semantics.
Empty and partial Pages
A newly registered Agent can be verified while initial scoring is still pending. Show the identity and ownership receipt immediately, reserve stable space for both donuts and label the score state. If Creator or lineage context is unavailable, keep that section useful with a direct explanation; never fabricate a relationship.