The Japanese AI-readiness data layer.
REST API over our corpus of crawled Japanese domains —
llms.txt adoption, schema coverage, page-level signals,
and AI-search readiness scores. Built for AI agents, SEO tools,
and research teams who need structured data on how the Japanese web
is preparing for ChatGPT, Gemini, and Perplexity.
Quickstart
Every endpoint is a stable JSON REST contract. No SDKs needed.
curl https://api.seoai.space/v1/health
curl -H "Authorization: Bearer $SEOAI_API_KEY" \
https://api.seoai.space/v1/domain/example.jp
Authentication
Every authed endpoint requires a Bearer token in the Authorization
header. Query-string ?api_key= is rejected (it leaks into logs).
Each successful call deducts 1 prepaid call.
Authorization: Bearer sk_seoai_XXXXXXXXXXXXXXXXXXXXXXXXXXXX
Create a key on seoai.space → API. New keys include 5 trial calls. Top up prepaid packs anytime. OpenAPI: /v1/openapi.json. Account: GET /v1/me (no charge).
Visitor / own UI:
POST https://seoai.space/api/embed/check
(optional partner_token, 10/min/IP, up to 180s).Server / volume:
POST https://api.seoai.space/v1/score
(API key, same engine). Do not use POST /v1/demo for this —
that is a lighter public demo, not the Free Score payload.
Endpoints
{"ok": true} when the API and corpus DB are reachable.has_meta_desc,
has_h1, JS-rendered ratio), and a sample of recent pages.
{url, locale?, async?}. Locale en|ja|vi.
async:true → 202 + job_id, poll GET /v1/jobs/<id>.
Up to 180 seconds. Preferred host: this origin.
bge-m3 model we use, then return top-k
matching pages.
Pricing
One rule: 1 successful authed call = 1 prepaid call.
New keys include 5 trial calls. Four packs only — cap is 40,000
calls. Same list as seoai.space/apipricing.
No monthly subscription. monthly_quota on a key
is a recorded ceiling, not a monthly grant of free calls.
- $0.025 per call
- 5 trial calls on a new key
- $0.02 per call
- Volume discount
- $0.013 per call
- Volume discount
- $0.0125 per call
- Largest self-serve pack
Example response
{
"ok": true,
"meta": {
"domain": "example.jp",
"tranco_rank": 84219,
"country_code": "JP",
"discovered_at": "2026-04-12T03:14:00Z",
"last_crawled_at": "2026-05-15T03:35:44Z",
"crawl_status": "done"
},
"signals": {
"pages_total": 18,
"pages_with_meta_desc": 17,
"pages_with_h1": 16,
"pages_js_rendered": 0
},
"pages": [
{
"url": "https://example.jp/",
"http_status": 200,
"fetched_at": "2026-05-15T03:35:44Z",
"title": "株式会社例 — 公式サイト",
"lang": "ja"
}
]
}
Errors
| Status | Body | Meaning |
|---|---|---|
| 401 | missing_api_key | No Bearer token. |
| 401 | invalid_api_key | Key is unknown or revoked. |
| 402 | out_of_credits | Prepaid balance is 0 — top up. |
| 404 | not_found | Domain or job not found. |
| 429 | rate_limited | Per-IP burst cap. Retry-After is set. |
| 503 | embedding_service_unavailable | Search needs a GPU; none rented right now. |
Status
Live status: api.seoai.space/v1/health · api.seoai.space/v1/stats