Client setup

claude mcp add \
  --transport http valuly \
  https://valuly.ai/api/mcp \
  --header "Authorization: Bearer val_live_..."

{
  "mcpServers": {
    "valuly": {
      "url": "https://valuly.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer val_live_..."
      }
    }
  }
}

curl https://valuly.ai/api/mcp/tools

Values a domain against 94,567 recorded market sales. Returns a market band (25th–75th percentile of real sales for names of the same class and length), a grade, and an exact-match screen of the US federal trademark register. Every response restates the model's measured error, so a caller reading only the midpoint still carries its uncertainty.

Lists the key holder's domains with last recorded valuation, grade, acquisition cost, tags and renewal date. No arguments.

Returns recorded valuation snapshots for one domain, oldest first. Snapshots come from appraisals actually run, so a domain appraised once has one point — the tool says so rather than returning an empty list without explanation.

Computes 12, 24 and 36-month lease-to-own schedules from the valuation midpoint, or from an agreed sale price you supply. Arithmetic only: the 24 and 36-month terms carry 10% and 18% financing fees. Valuly does not broker, escrow or guarantee any transaction.

Lists portfolio domains whose registrar-reported expiry falls inside a window you choose. Dates are a snapshot from your last registrar import, not a live feed — credentials are never stored, so nothing refreshes them in the background. Every response reports how many domains actually have expiry data, because “nothing is expiring” and “we have no data” are different answers.

Whether the same name is registered under other extensions, from a live lookup against each registry’s own RDAP service with DNS delegation as a second check. Every result is one of three values, and the third one is the point: registered, unregistered, or unverified — which means we could not find out, and never means available. Some extensions (.io, .co, .me) publish no RDAP service at all, so registration cannot be confirmed for them by design; a timeout or registry error returns unverified too. Nothing collapses into “available”.

Two limits travel in every response. unregistered is not purchasable — premium, reserved and pending-delete names all read as unregistered without being available at the standard fee, and no price is checked. And “responds on https” is not “developed”, because a parked or for-sale page responds too. Rate limited separately at 60 calls per hour: each call queries domain registries directly, and their terms prohibit high-volume automated querying.

On find_buyer_prospects

This tool was previously listed and is still not exposed — but the reason has changed, and half of it now ships. Its only implementation returned a fixed table asserting which TLD variants were “taken and developed”, identically for every domain, without checking anything. That part is fixed: registration status is a real registry lookup, and it is available above as check_sibling_tlds, named for what it returns rather than for what you might do with the answer.

What is still missing is the other half. The buyer categories behind it are the same three strings for every domain, so a tool by that name would imply it had identified specific prospects for your name when it had not — the same over-claim, moved from the data to the label. It ships when the category signal is real and per-domain.

Body: { "domain": "example.com", "askingPrice": 5000 } — askingPrice optional. Returns the market band, grade, score and trademark screen.

Body: { "domains": ["a.com", "b.io"] }. 100 domains per request on Business, 25 on Pro. Bulk is a paid feature: Free returns 402 UPGRADE_REQUIRED, and an over-sized batch returns 400 BATCH_TOO_LARGE with the limit rather than silently truncating. Each domain gets a full valuation with its own trademark screen, not a bulk-rate approximation.

The MCP server. See §3.

Unauthenticated. Returns the tool list, endpoint and auth scheme.

Unauthenticated liveness check.

curl -X POST https://valuly.ai/api/appraise/single \
  -H "Authorization: Bearer val_live_EXAMPLE_KEY_NOT_REAL" \
  -H "Content-Type: application/json" \
  -d '{"domain": "workspaces.ai", "askingPrice": 5000}'

const response = await fetch('https://valuly.ai/api/appraise/single', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer val_live_EXAMPLE_KEY_NOT_REAL',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({ domain: 'workspaces.ai', askingPrice: 5000 })
});
const result = await response.json();

import requests
res = requests.post("https://valuly.ai/api/appraise/single",
    headers={"Authorization": "Bearer val_live_EXAMPLE_KEY_NOT_REAL"},
    json={"domain": "workspaces.ai", "askingPrice": 5000})
data = res.json()

curl -X POST https://valuly.ai/api/mcp \
  -H "Authorization: Bearer val_live_EXAMPLE_KEY_NOT_REAL" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "appraise_domain",
      "arguments": { "domain": "workspaces.ai" }
    }
  }'

Limits

• Valuations: 60 requests / minute on Free, 300 requests / minute on Pro, 1,200 requests / minute on Business.
• Monthly allowance: 5 appraisals / mo on Free, 100 appraisals / mo on Pro, 500 appraisals / mo on Business.
• MCP requests: 240 per hour. Tool calls that run a valuation also draw on both limits above.
• Registrar imports: 20 per hour.

The per-minute figure is a burst ceiling; the monthly allowance is how much you may actually run. They are separate: exceeding the ceiling returns 429, exhausting the allowance returns 402 with code QUOTA_EXCEEDED and the date it resets. API traffic draws on the same allowance as the application — it is not extra capacity. Other endpoints (authentication, registrar import, invitations, key creation) have their own budgets, the same on every plan. Every response carries RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset, so you can back off precisely rather than guessing.

Status codes

Webhooks

Outbound webhooks are not available. Valuations are computed synchronously and return in the same response, so there is no asynchronous job to notify you about. If you want notification on a schedule, use scheduled re-appraisal in the app.