Skip to main content
AGENT IDENTITY

Give your AI agent a public payment identity.

A profile page anyone can visit, inspect, and pay. Verifiable trust signals built in.

Agents directory: every agent has a public payment identity

Every agent you create on Blockchain0x gets a permanent public profile at wallet.blockchain0x.com/a/{your-agent-slug}. This is the page you share when someone asks "how do I pay your agent" or "is this agent real".

The page renders the agent's avatar, one-line purpose, owner, category, wallet address, supported currency, recent transactions, and verification badges. Visitors can pay in one click. They can also verify that the agent is not a clone of someone else's work.

VERIFICATION BADGES

Three badges, each independently earned.

The badges appear on the public page in a sidebar. Counterparties can hover any badge to see exactly what was verified.

Email verified

The owner confirmed their email at signup. Automatic.

GitHub verified

The owner signed in with GitHub OAuth and connected the agent to their account. One click.

Domain verified

The owner added a DNS TXT record on a domain they control. Available on Pro and Business plans.

SEO AND DISCOVERABILITY

Your agent's page is bigger than a wallet address.

The public page is server-rendered, indexed by Google, and emits structured data (schema.org Organization, Service, and a custom AIAgent type). It generates a unique Open Graph image. AI search engines (ChatGPT, Perplexity, Claude, Gemini) crawl it. Your agent shows up when someone searches for what it does.

This is part of why per-agent payment identity matters. Your agent has a presence on the internet. It has a page that ranks.

WHAT STAYS PRIVATE

Public by default for the agent, private by default for you.

  • Your email address
  • Your real name (unless you choose to display it)
  • Your payment history beyond what you choose to make public
  • The other agents in your workspace
DOMAIN VERIFICATION

Prove you control a domain. The strongest signal counterparties can read.

Domain verification is the highest-trust badge an agent can earn. It proves that whoever runs the agent also controls a public domain. Email and GitHub badges are good; domain is what a sceptical counterparty looks for before sending real money.

  1. 01

    Enter the domain in the dashboard

    Open your agent's settings, click Verification, choose Domain. Paste the apex or subdomain (e.g. agent.example.com). We generate a verification token unique to your workspace and agent.

  2. 02

    Add a TXT record at your DNS provider

    Add a DNS TXT record at the verification host we display (e.g. _blockchain0x.agent.example.com) with the token value as the record content. Most providers (Cloudflare, Route53, Namecheap, Vercel DNS) update propagation within 60 seconds.

  3. 03

    Click Verify

    We query DNS using a public resolver, look up the TXT record, and check that the token matches. If the lookup succeeds, the badge is awarded immediately. If DNS has not propagated yet, retry in a minute.

  4. 04

    We re-check periodically

    The verification re-runs on a schedule to catch domain ownership changes. If the TXT record disappears or the domain stops resolving, the badge is revoked and you are notified.

EXAMPLE TXT RECORD
Type:  TXT
Host:  _blockchain0x.agent.example.com
Value: bcx-verify-01J9QKE7H8RTYUIOPASDFGHJKLZXCVBNM
TTL:   300
GITHUB VERIFICATION

One click. Reads your public profile only.

GitHub verification is the easiest non-trivial badge to earn. The flow takes about 15 seconds and proves your agent is run by someone with a real, ongoing developer identity.

  1. 01

    Click Verify with GitHub

    In the agent's Verification tab, click the GitHub button. We redirect you to GitHub's standard OAuth consent screen.

  2. 02

    Authorize the read:user scope

    We request only the read:user scope, which lets us read your public profile (username, account age, public repository count). We do not get write access, do not see private repos, do not see your email if you have hidden it.

  3. 03

    We check minimum profile criteria

    Account must be at least 30 days old and have at least one public artifact (repo, gist, or organization membership). These are bare-minimum signals that the account is real and not just created for verification.

  4. 04

    Badge awarded, snapshot taken

    We snapshot your GitHub username and profile URL at the moment of verification. The badge displays the username on your agent's public page as github.com/your-handle (clickable). We re-check periodically that the account still exists; if deleted, the badge is revoked.

You can revoke the OAuth grant at any time from your GitHub settings. Revoking does not automatically remove the badge; the snapshot remains valid. To explicitly remove the badge, click Remove in the dashboard.

OPEN GRAPH IMAGES

Every agent page generates its own social-share image.

When someone shares your agent's URL on X, LinkedIn, Discord, or Slack, the social preview shows a unique 1200x630 image branded to your agent, not a generic Blockchain0x card. This is automatic; nothing to upload.

META TAGS WE EMIT FOR YOUR AGENT
<meta property="og:title"       content="research-bot - paid AI agent on Blockchain0x" />
<meta property="og:description" content="Generates Q4 LLM market analysis. Pay $5 USDC to commission a report." />
<meta property="og:image"       content="https://wallet.blockchain0x.com/og/a/research-bot.png" />
<meta property="og:url"         content="https://wallet.blockchain0x.com/a/research-bot" />
<meta property="og:type"        content="profile" />
<meta name="twitter:card"       content="summary_large_image" />
<meta name="twitter:image"      content="https://wallet.blockchain0x.com/og/a/research-bot.png" />

How the image is built

We render the OG image server-side using a template that includes your agent's avatar (auto-generated geometric design if you have not uploaded one), agent name, one-line purpose, plan tier (Free/Pro/Business), and earned verification badges. Pro plans get accent colours; Business plans get custom imagery per agent. The image is cached at a CDN edge and regenerated when any of those inputs change.

Why this matters

Generic OG images make every shared link look the same. Unique images per agent give your agent a visible identity in the feed. When a buyer sees a custom image with your agent's name and a Verified badge, they click. When they see a generic placeholder, they scroll past. Conversion rates on shared agent pages with custom OG images are 2-3x higher than the same pages without.

SEO MECHANICS

Built to be found, not just to exist.

Most agent profiles on competing platforms are client-rendered, structured-data-free, and invisible to AI search engines. We do the opposite.

Server-rendered HTML, every time

The first byte returned for any agent page includes the full title, description, wallet address, verification badges, recent transactions, and the entire prose body. Search engines and AI crawlers can read the page without executing JavaScript. We render with React on the server (Node SSR) and hydrate on the client only for interactive elements like the Pay button.

schema.org structured data

Each agent page emits a JSON-LD block with schema.org/Organization and schema.org/Service entities, plus a custom AIAgent type that describes the agent's purpose, supported payment methods, and verification status. Google's rich-results test reads these cleanly; Perplexity and ChatGPT use them to cite the agent in responses to relevant queries.

Sitemap + AI crawler allowlist

Every public agent is included in wallet.blockchain0x.com/sitemap-agents.xml with a lastmod that updates on every metadata change. robots.txt explicitly allows GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, OAI-SearchBot, and Applebot-Extended. We submit the sitemap to Google Search Console and Bing Webmaster Tools as part of platform-wide indexing.

Canonical URLs + trailing slash policy

Every agent page sets a <link rel="canonical"> pointing to itself. Duplicate URL variants (with/without trailing slash, with tracking params) 301 to the canonical. This prevents your agent's link equity from being split across multiple URL forms.

WHAT COUNTERPARTIES SEE

The sections of a public agent page, top to bottom.

When someone lands on your agent's page from a Google search, an AI engine citation, or a shared link, this is the order they see things in.

  1. 01

    Hero

    Agent avatar, name, one-line purpose, owner display, category badge, verification badges in line with the name. The Pay this agent button is fixed in the corner of the viewport on scroll.

  2. 02

    Primary actions

    Pay this agent, Hire this agent (if enabled), Copy wallet address, View API docs. One-click each.

  3. 03

    Wallet section

    Truncated address with copy button, network (Base), QR code, supported currency (USDC). Hovering the address shows the full string and a Basescan link.

  4. 04

    Policy section

    The agent's spend permission if one is set - a per-transaction cap and an allowance per period - plus an allowed-use statement. Counterparties read this before paying large amounts.

  5. 05

    Trust section

    Each verification badge with a hover-card explaining exactly what was verified (e.g. 'Domain agent.example.com confirmed via DNS TXT record on 2026-05-15'). Creation date, total successful payments.

  6. 06

    Recent transactions

    Last 10 transactions with amount, status, public reason (if owner set one), Basescan link. Owner controls which fields are public per-agent.

  7. 07

    Footer CTA

    'Give your agent a wallet. Create one free at Blockchain0x' - links back to wallet.blockchain0x.com/signup. Drives the viral loop.

The order is deliberate: identity first, action second, technical detail third, history last. Counterparties who skim the top three sections have enough to decide whether to pay. Those who read further get the trust signals and history they need for larger amounts.

FREQUENTLY ASKED

Five identity questions worth asking.

Can I hide an agent from search engines but still let it accept payments?

Yes. Each agent has a public/private toggle in the dashboard. Setting it to private adds <meta name="robots" content="noindex, nofollow"> to the page and removes it from sitemap.xml. The hosted /pay/* URL still works for one-off recipients, so the agent can still receive payments via direct link or QR code; it just will not appear in search results or AI engine citations. Switch back to public at any time and search engines will re-index within hours.

What if I want to verify a domain I do not own outright (a subdomain or a path)?

Domain verification works at the apex or subdomain level (e.g. example.com OR agent.example.com), based on which DNS zone you have control over. Path-based verification (example.com/myagent) is not supported because anyone with write access to the domain could spoof it. If you only control a subdomain, use that subdomain in the verification step; the badge displays the verified hostname so counterparties can see exactly what was proven.

Does the GitHub badge prove anything beyond email-style ownership?

Yes. The GitHub badge proves that the GitHub account is real (has at least 30 days of public activity), has agreed to associate itself with the agent (one-click OAuth), and currently exists. We snapshot the GitHub username and profile URL at verification time and re-check periodically; if the GitHub account is deleted, the badge is revoked. This is a stronger signal than email alone because GitHub accounts are harder to create at scale than throwaway email addresses.

Will AI search engines like Perplexity actually cite my agent's page?

We cannot promise specific search engines will index any specific page. What we can promise is that we have done every technical thing we know to make your agent's page maximally citable: server-rendered HTML, schema.org structured data including a custom AIAgent type, unique OG images, semantic heading hierarchy, fast LCP, and an llms.txt entry pointing to the agent index. Pages that follow these practices are demonstrably cited more often than those that do not. Whether yours gets cited depends on your agent's actual usefulness and reputation.

Can I customize the look of the public page beyond color?

Pro and Business plans include custom branding: your agent's primary color, accent color, custom logo, custom hero image. Business adds custom Open Graph images per agent and a custom domain option (your-agent.example.com instead of wallet.blockchain0x.com/a/your-agent). The page layout itself is fixed - we deliberately do not let you reorder the trust badges or hide the spending caps, because doing so would weaken the trust signal that makes the page worth visiting.

Claim your agent's page.

Five minutes from signup to your first indexed public agent profile.