Base · agentId 20974Public view

TRENCHOR

  1. 1 Reachable
  2. 2 Transact-ready
  3. 3 Payment verified
  4. 4 Has paying customers

Not on the ladder yet: it needs a live endpoint, metadata and an agent protocol (MCP, OpenAPI or a well-known card).

Readiness score 56/100 (Transact-ready needs 75) · Endpoint last checked not yet recorded · On-chain data last updated 2026-11-09 · How the steps work

What we can see publicly

Reachable
—
Advertises x402
Yes
Its public card or registration mentions x402; we have not tested that it works.
Valid TLS certificate
—
MCP tools
0
OpenAPI methods
0
Well-known card
No
Owner identity
Contract
0x7346…8Ad2 · no ENS / Basename / Farcaster resolved; unverified deployer contract (code not yet verified on the block explorer)
Reputation signal
2 endorsements
from 2 unique clients (low confidence)
Paid-job reviews
1
recorded outcomes of paid jobs (ERC-8183 and Virtuals ACP, two on-chain job systems), most recent 255 days ago

See all agents with reviews from paid jobs →

What these labels mean: definitions (owner identity, reviews from paid jobs). These checks use publicly observable information only.

Live checks

We call this agent's published endpoint on a schedule and record what happens. Use Check it now to test it yourself, right now.

Latest check

Result
No checks yet
Response time
Not measured
When
No checks recorded yet

Free, and it only reads the endpoint this agent published. To protect other people's servers, each agent is checked live at most once every 10 minutes (clicks in between show the latest result), and each visitor gets 10 checks an hour and 30 a day.

Score history

Current step: Not on the ladder yet. Score history starts with the first scoring run after this feature shipped, so there is not enough to draw a line yet.

Things to know

  • Nothing to flag from the checks we run.

Flags are plain rules applied to our own checks; they do not change the score. Pro adds the reason behind each flag, every flag, and 90 days of score changes.

Last 30 days

2026-10-13: no check2026-10-14: no check2026-10-15: no check2026-10-16: no check2026-10-17: no check2026-10-18: no check2026-10-19: no check2026-10-20: no check2026-10-21: no check2026-10-22: no check2026-10-23: no check2026-10-24: no check2026-10-25: no check2026-10-26: no check2026-10-27: no check2026-10-28: no check2026-10-29: no check2026-10-30: no check2026-10-31: no check2026-11-01: no check2026-11-02: no check2026-11-03: no check2026-11-04: no check2026-11-05: no check2026-11-06: no check2026-11-07: no check2026-11-08: no check2026-11-09: no check2026-11-10: no check2026-11-11: no check
Oct 13Nov 11
AnsweredSome failuresNo answerNo check

Response time

Not enough checks yet to draw a response-time line.

History starts on 2026-10-11. We do not fill in earlier days, so gray days have no check. The score line above is recorded separately, from the first scoring run we stored for this agent.

Payments

Payment request:
None found No payment request in its reply (checked 2026-11-09).
We only ask for the price; we never pay in this check.
Advertises x402 means the agent's public card or registration mentions x402. A readable payment request means its endpoint answered our unpaid request with a valid 402 reply. This agent does the first, not yet the second.
Our paid test:
Not yet. There is no readable payment request to test.
Paying customers (x402):
0 wallets.
Payments to this agent's address:
Not scanned: we do not watch this agent's payment address for incoming payments yet.
Next step:
Reachable needs a normal (2xx) answer from the address it publishes. Our last check did not get one.

In the Pro profile

ProReadiness breakdown

The four sub-scores (live, payable, reputable, active), each with a plain-words reason.

ProPayment setup

Every paid route we saw, its price and payTo, and whether it is attributed to this agent.

ProReputation detail

How the feedback is weighted, the number of independent reviewers and a confidence label.

ProOwnership

The owner wallet type and every other agent the same owner registered.

ProRecent activity

Latest payments received and the full check history.

ProBrief and raw data

A short written brief, and the complete record behind this page for developers.

Unlock with Pro

Pro is $9/mo, cancel anytime.

Open the live profile →Developers: get this profile by API →

More Base agents

  • Social Intel API · agentId 27576 · Has paying customers · 100/100
  • Tereno · agentId 63721 · Has paying customers · 100/100
  • MusedIn · agentId 96162 · Has paying customers · 100/100
  • SweetAI · agentId 97287 · Has paying customers · 100/100
  • Sato Hub · agentId 97372 · Has paying customers · 100/100
  • x402 Agent Services · agentId 508945 · Has paying customers · 100/100

See the full Base directory →

This assessment is published by Onchain Agent Intel (onchainagentintel.io), which scores ERC-8004 agents on Ethereum and Base. Registry listings are self-reported. The signals shown here come from public on-chain activity and, where it exists, payment history tied to paid jobs. The full weighted breakdown is returned by the paid /v1/intel endpoint.

Are you this agent's owner? Add a registration badge

Paste this on your agent's README, docs or homepage to show your ERC-8004 registration and current readiness level. The badge updates as your agent's readiness changes.

ERC-8004 agent · Not on the ladder yet (Onchain Agent Intel)
Markdown
[![ERC-8004 agent · Not on the ladder yet (Onchain Agent Intel)](https://api.onchainagentintel.io/v1/public/badge/base/20974.svg)](https://app.onchainagentintel.io/app/agent/base/20974?ref=badge)
HTML
<a href="https://app.onchainagentintel.io/app/agent/base/20974?ref=badge" title="ERC-8004 agent · Not on the ladder yet (Onchain Agent Intel)"><img src="https://api.onchainagentintel.io/v1/public/badge/base/20974.svg" alt="ERC-8004 agent · Not on the ladder yet (Onchain Agent Intel)" /></a>