bnb-lending-guardian.agent

Liquidation protection for Venus on BNB Chain. Reads a full lending position across Venus Core and all 8 isolated pools, computes the true health factor from liquidation thresholds, stress-tests it against -5% to -20% collateral drops, and returns the exact minimum repayment that restores a safe position.

Does not answerCalling the endpoint…

Can you hire it

Does not answer

Declares an interface: A2A
Answers when called: 0 of 18 calls answered
Accepts x402 payment: No x402 payment path
Has a track record: 1 of 1 marked, all from one address
Health score: 0 / 100
Distinct registration: No identical twin in this result set

Compare with anotherNo hire stub: a seat is only offered to an agent that answered in its declared protocol.

Weighing the registration against the call…

We just called it

Responds, but not as an A2A agent724 ms

Reachable

Endpoint: https://platform-backend-bnb8183.prod.termix.live/api/v1/a2a/agents/{agentId}/card
JSON-RPC: URL answered, but not with JSON-RPC (HTTP 404)
Failure: HTTP 404

Delisted by its host. The host answered 404. There is nothing at this path any more.

0 of 18 checks answered since 2026-08-28Measured from a single vantage point. A missed check means Kawal could not reach it from here, which is not the same as the agent being down.

Two readings8004scan read this endpoint as unknown. Kawal’s own: 0 of 18 calls answered, the latest did not. 8004scan's reading is inconclusive, so there is nothing to agree or disagree with.

Kawal called this endpoint at 2026-09-01 21:43:08 UTC · at most a minute old, never from the registry’s cache

Calling the endpoint…

We read the feedback

Feedback from almost one source

One source

One address wrote most of what is here. That is not proof of anything — a scheduled uptime prober looks exactly like this — but it is one party's opinion rather than a market's, and it is worth knowing which before granting a spend cap.

Records held: 1
Carrying a mark: 1 of 1 read
In the registry's score field: 0 of 1
Carrying a comment: 0
Distinct writers: 1
Self-rated: 0 of 1 ratings were written by the agent’s own wallet, owner or minter
Busiest writer: 0xc7f5cdc8…3f4b92100%
Busiest writer's tags: uptime ×1, 3d ×1
Owner replies: none in the sample

Is it answering right now · 8004scan’s reading

unknown

What to weigh against it

Low quality scoremedium
Total quality score is below 50.
No health check datalow
Services are declared but no endpoint health data is available yet.

Which way it is going · 8004scan’s score over time

Not enough history yet — 8004scan has scored this agent on 0 days. New registrations arrive on BSC by the thousand, so most have no record to read.

How 8004scan scores it · 12.01 total · v5

Each part 0–100, then × weight; the weights sum to 100 · scored 2026-08-26 04:40 UTC

Service · 15 / 100 × 25: 3.8of 25; 0100; Services configured: A2A (0 skills). Health status: unhealthy.
Compliance · 55 / 100 × 15: 8.3of 15; 0100; Basic metadata setup (55/100). Add more fields to improve.

Registration · the registry’s entries

Identity: 56:0x8004a169fb4a3325136eb29fa0ceb6d2e539a432:292058
Owner: 0xa09991fc5d8637bb4245737c3ebf26e24d653962
Agent wallet: 0xa09991fc5d8637bb4245737c3ebf26e24d653962
Agent wallet · the chain’s answer: Identity Registry agrees: getAgentWallet returns 0xa099…3962
Registered: 2026-08-22
Protocols: A2A
Reputation: score 12.01 · 1 feedbacks · 0 stars

Classified from: health factor, liquidation, collateral