Agentic Portal

Agent Trust and Compliance

security
Serving

Checks an agent can run before it trusts a counterparty. POST /v1/domain-trust: RDAP and DNS (MX, SPF, DMARC, DNSSEC) as a 0-100 score. /v1/brand-verify: a live TLS handshake. /v1/seller-trust: both, with a recommendation. /v1/sanctions-check: the US Consolidated Screening List. /v1/reputation: an EVM address on eth, base, arbitrum or polygon. Scores come with reasons.

Endpoint
POST https://agent.pocket.network/v1/agent-trust/v1/domain-trust
Price per call
$0.005 USD
Networks payable on
Base (eip155:8453), Tempo (eip155:4217)
Protocol
rest

Calling it

The first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.

Example request

A real, working call — the request the service card verifies against.

curl -X POST https://agent.pocket.network/v1/agent-trust/v1/domain-trust \
  -H 'content-type: application/json' \
  -d '{"domain":"example.com"}'
Example response

The response this call returned, captured 2026-11-09 19:45:39 UTC.

{
  "portal": {
    "provenance": "third-party-supplier",
    "serviceId": "agent-trust",
    "schemaCheck": "unchecked"
  },
  "data": {
    "service": "agent-trust",
    "fetched_at": "2026-11-09T19:45:38.463Z",
    "cache": {
      "stale": false,
      "age_ms": 0
    },
    "domain": "example.com",
    "trust_score": 100,
    "trust_score_scale": "0-100, higher is more trustworthy",
    "registration": {
      "registered": true,
      "ldh_name": "EXAMPLE.COM",
      "status": [
        "client delete prohibited",
        "client transfer prohibited",
        "client update prohibited"
      ],
      "nameserver_count": 2,
      "has_secure_dns": true,
      "registered_at": "1995-08-14T04:00:00Z",
      "expires_at": "2027-08-13T04:00:00Z",
      "last_changed_at": "2026-08-14T08:01:43Z",
      "age_days": 11410,
      "days_until_expiration": 276
    },
    "dns": {
      "has_mx": true,
      "mx_count": 1,
      "has_spf": true,
      "has_dmarc": true,
      "a_record_count": 2
    },
    "reasons": [
      "registered 11410d ago (+40.0)",
      "has MX records (+10)",
      "has SPF record (+5)"
    ]
  }
}

Try it

Make one real paid call from your own wallet — about $0.005 on Base (eip155:8453). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.

No browser wallet found. Install MetaMask, Rabby, or Coinbase Wallet to try a call here.

Supported methods

Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.

Methods Agent Trust and Compliance accepts, and whether each reads or writes.
MethodEffect
GET /v1/healthread
GET /v1/versionread
POST /v1/brand-verifyread
POST /v1/domain-trustread
POST /v1/reputationread
POST /v1/sanctions-checkread
POST /v1/seller-trustread

Schemas

Published by the service itself. The example above is generated from these.

Request schema
{
  "type": "object",
  "description": "The body of POST /v1/domain-trust and /v1/brand-verify (domain, and for brand-verify an optional brand_name). /v1/seller-trust takes url; /v1/sanctions-check takes address (a wallet address, entity name or other identifier); /v1/reputation takes chain (eth, base, arbitrum or polygon) and address.",
  "properties": {
    "domain": {
      "type": "string",
      "description": "The domain to check, e.g. example.com."
    },
    "brand_name": {
      "type": "string",
      "description": "brand-verify only. The brand the certificate should name."
    }
  },
  "required": [
    "domain"
  ]
}
Response schema
{
  "type": "object",
  "description": "Each check answers its own JSON object with a 0-100 score and a reasons array: domain-trust a trust_score from RDAP and DNS, brand-verify the TLS facts, seller-trust both with a trusted, proceed_with_caution or high_risk recommendation, sanctions-check the list matches, reputation the address facts and coverage. Errors carry an error field."
}