api

与网站相同的 JSON

REST、JSON、Bearer 密钥。在你的账户中创建密钥,然后调用下面任意端点。机器可读的规范见 /api/v1/openapi.json(OpenAPI 3.1)。

各计划配额
计划API 调用 / 月点数 / 月批量上限端点
试用30050100 / 批appraise, usage, bulk, drops
Starter1,000300500 / 批appraise, usage, bulk, drops

点数支付引擎的工作:每次估值一个,批量中每个域名一个。API 配额按请求计数。两者每月重置。

快速开始
估值一个域名bash
curl -X POST https://resaleodds.com/api/v1/appraise \
  -H "Authorization: Bearer dsk_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain": "creditseason.com"}'
提交批量任务(Pro 及以上)bash
curl -X POST https://resaleodds.com/api/v1/bulk \
  -H "Authorization: Bearer dsk_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domains": ["a.com", "b.com", "c.com"]}'
查询用量(免费)bash
curl https://resaleodds.com/api/v1/usage \
  -H "Authorization: Bearer dsk_YOUR_KEY"
mcp 服务器
https://resaleodds.com/api/mcpStreamable HTTP
claude mcp add --transport http domainvalue https://resaleodds.com/api/mcp \
  --header "Authorization: Bearer dsk_YOUR_KEY"

工具 appraise_domain、list_drops 和 get_usage,配额与 REST 端点相同。详情和其他客户端见面向智能体的页面。

端点
  • post/api/v1/appraise

    Appraise a single domain

    Costs 1 API call + 1 credit. Cached results (24h, same calibration) are free.

  • post/api/v1/bulk

    Submit a bulk appraisal job

    Pro plan and above. 1 API call + 1 credit per domain. Results ranked by opportunity (value × probability of sale).

  • get/api/v1/bulk/{id}

    Poll a bulk job

  • get/api/v1/drops

    Daily curated expired domains

    Pro plan and above. Safe-zone filtered, opportunity-ranked. Source is a deterministic mock until CZDS zone-file access is granted (clearly labeled).

  • get/api/v1/demand/{domain}

    Solvent demand: buyer candidates and upgrade-domain targets

    Business plan. Who could buy this name (with budget bands) and which degraded variants (hyphenated, other TLDs, prefixed) host active sites — the documented upgrade-buyer profile. Candidates are flagged `simulated: true` until live company search is enabled.

  • get/api/v1/usage

    Current API usage and quota

    Free of charge (cost 0).

错误与配额头

错误始终为 {"error": {"code", "message"}} 的形式,并带有明确的 HTTP 状态码:401 密钥,402 点数,403 计划,422 输入,429 配额。每个已授权的响应都带有 X-RateLimit-Limit / Used / Remaining / Month。