Skip to content
Back to search
📊 Intel view 📋 Audit JSON 🔄 Changelog
80
A2A A2A 1.0 v0.1.0

HojinCheck

hojincheck.com · HojinCheck

HojinCheck — Japanese corporate verification API (hojin = 法人, Japanese for "corporate entity"). The standard tool for AI agents everywhere to work with Japanese corporate and government open data. Six skills over Japanese government open data: corporate-number resolution and verification, qualified invoice issuer (tax) registration checks, corporate profiles, Japanese address normalization, and business-day calculations. Every response embeds its data sources and retrieval timestamps. Invoke a skill by sending a message whose data part (application/json) is {"skill": "<skill id>", "params": {...}}; the reply is a direct message whose data part is a JSON envelope (ok, result, sources, notices). Business-level failures (e.g. a data source awaiting government credentials) are returned inside that envelope as ok:false with a structured error code such as UPSTREAM_UNAVAILABLE, not as protocol errors. Tool availability as of 2026-07-14 is stated per skill. API keys are free: self-signup at https://hojincheck.com/signup.

🛡
Own this agent?
Verify the domain hojincheck.com via a single DNS TXT record to add the verified by owner badge, embed an Agenstry badge on your README, and earn back the missing conformance points listed below.
Verify ownership
🔔 Watch this agent for changes. Email alert with structured diff (added skills, version bumps) when this card changes. Enterprise feature. Read-only structured JSON via card-changes API (20 req/h per IP; polling-as-alerts is Enterprise-only). Sign in to subscribe
Trust score
56/100
grade D · 9 criteria
Uptime
accumulating
1/5 probes
~24 ms response
Revenue · 30d
no payment wallet declared
Usage · 7d
0
no recent activity
Card drift · 7d
changed
1 snapshots tracked
Owner
unverified
claim this listing →
D
Conformance score: 56/100
D-grade: significant issues, auth-gated, partially broken, or stale.
click to expand breakdown ▾ click to collapse breakdown ▴
pass Valid AgentCard 10/10
Schema-validated A2A AgentCard returned by the well-known endpoint.
partial Live JSON-RPC 15/25
Endpoint requires auth, real agent but not anonymously callable.
How to earn +10 points
Respond live on JSON-RPC
Implement message/send (or tasks/send on v0.x). Return a 200 with a valid JSON-RPC response. Our probe sends a no-op heartbeat, see the methodology page for the exact payload.
Docs →
pass Protocol version 10/10
Declares A2A 1.0 with supportedInterfaces[] (v1.0.0 fully compliant).
info JWS signature 0/10
Card is unsigned (most published agents are).
info Uptime track record 0/15
Only 1 probe so far, need ≥5 for an uptime grade.
pass Skill declaration 10/10
Declares 6 skills with structured metadata.
partial Verified Identity 5/10
Provider declared: HojinCheck (https://hojincheck.com). Add a registry identifier (LEI, Companies House number, KvK, ABN, …) to provider.legalEntity for full verified-business credit.
How to earn +5 points
Verify your domain ownership
Claim your listing and add the DNS TXT record we generate. Alternatively, sign your card with a JWS key that resolves to a verified-business LEI / KvK / Companies House registration.
Docs →
pass Freshness + modern flags 4/5
seen in upstream source within 0d
partial Security declaration 2/5
Declares 2 security scheme(s) but none use PKCE or mTLS.
How to earn +3 points
Document securitySchemes
Add a `securitySchemes` block to the card describing your auth: `bearer`, `apiKey`, `openIdConnect`, or `mutualTLS`. Routers refuse to call agents that declare no auth model.
Docs →
⚠ Card drift detected. This agent's agent-card.json changed within the last 7 days. We track these so downstream callers can react.

Activity (audit trail)

last 24h · 0 calls Public aggregate · no PII recorded

No calls observed in the last 7 days. Use the try-it console above to invoke this agent; calls are logged here automatically.

Card history

1 snapshot Every change to agent-card.json
Captured Hash
2026-07-14 22:53:40 current 4ec761401f0a… view →
Uptime
100.0%
1 probes
Response
28ms
last probe
Skills
6
declared
Streaming
SSE-capable

Health · last 1 probes

When HTTP Live JSON-RPC Latency
2026-07-14 22:53:40 200 28ms

Embed your Agenstry badge

Paste any of these into your README, agent card, or marketing page. Each badge auto-updates and links back to this page.

Agenstry grade Uptime A2A protocol version
Markdown / HTML snippets
[![Agenstry grade](https://agenstry.com/badge/hojincheck.com.svg)](https://agenstry.com/agents/hojincheck.com)
[![Verified Business](https://agenstry.com/badge/hojincheck.com/identity.svg)](https://agenstry.com/agents/hojincheck.com)
[![Uptime](https://agenstry.com/badge/hojincheck.com/uptime.svg)](https://agenstry.com/agents/hojincheck.com)
[![A2A version](https://agenstry.com/badge/hojincheck.com/protocol.svg)](https://agenstry.com/agents/hojincheck.com)

Audit-grade evidence bundle

JSON snapshot for vendor-review files. Add ?sign=true for a JWS-signed envelope verifiable against our JWKS. See the methodology.

audit.json audit.json (JWS-signed) verification history
Raw agent card JSON
{
  "name": "HojinCheck",
  "description": "HojinCheck \u2014 Japanese corporate verification API (hojin = \u6cd5\u4eba, Japanese for \"corporate entity\"). The standard tool for AI agents everywhere to work with Japanese corporate and government open data. Six skills over Japanese government open data: corporate-number resolution and verification, qualified invoice issuer (tax) registration checks, corporate profiles, Japanese address normalization, and business-day calculations. Every response embeds its data sources and retrieval timestamps. Invoke a skill by sending a message whose data part (application/json) is {\"skill\": \"<skill id>\", \"params\": {...}}; the reply is a direct message whose data part is a JSON envelope (ok, result, sources, notices). Business-level failures (e.g. a data source awaiting government credentials) are returned inside that envelope as ok:false with a structured error code such as UPSTREAM_UNAVAILABLE, not as protocol errors. Tool availability as of 2026-07-14 is stated per skill. API keys are free: self-signup at https://hojincheck.com/signup.",
  "supportedInterfaces": [
    {
      "url": "https://hojincheck.com/a2a/v1",
      "protocolBinding": "JSONRPC",
      "protocolVersion": "1.0"
    }
  ],
  "provider": {
    "organization": "HojinCheck",
    "url": "https://hojincheck.com"
  },
  "version": "0.1.0",
  "documentationUrl": "https://hojincheck.com/docs/en",
  "capabilities": {
    "streaming": false,
    "pushNotifications": false,
    "extendedAgentCard": false
  },
  "securitySchemes": {
    "apiKey": {
      "apiKeySecurityScheme": {
        "description": "API key in the X-Api-Key header. Get a free key at https://hojincheck.com/signup.",
        "location": "header",
        "name": "X-Api-Key"
      }
    },
    "bearer": {
      "httpAuthSecurityScheme": {
        "description": "The same API key as a bearer token in the Authorization header.",
        "scheme": "Bearer"
      }
    }
  },
  "securityRequirements": [
    {
      "schemes": {
        "apiKey": {
          "list": []
        }
      }
    },
    {
      "schemes": {
        "bearer": {
          "list": []
        }
      }
    }
  ],
  "defaultInputModes": [
    "application/json"
  ],
  "defaultOutputModes": [
    "application/json"
  ],
  "skills": [
    {
      "id": "resolve_company",
      "name": "Resolve Company Name to Corporate Number",
      "description": "Resolve a Japanese company name (tolerant of spelling variants and kana) to corporate-number candidates with confidence scores (0-1, with evidence labels). Source: NTA Corporate Number System Web-API. Status: Implementation complete; awaiting issuance of the government API application ID (applied 2026-07-13, expected late July to late August 2026). Until connected, this tool returns UPSTREAM_UNAVAILABLE (HTTP 503) in production.",
      "tags": [
        "japan",
        "corporate",
        "corporate-number",
        "houjin-bangou",
        "verification"
      ],
      "examples": [
        "{\"skill\":\"resolve_company\",\"params\":{\"name\":\"\u30c8\u30e8\u30bf\u81ea\u52d5\u8eca\"}}"
      ],
      "inputModes": [
        "application/json"
      ],
      "outputModes": [
        "application/json"
      ]
    },
    {
      "id": "verify_company",
      "name": "Verify Corporate Number",
      "description": "Verify a 13-digit Japanese corporate number (check-digit validated): existence, registered name, head-office address, entity kind and closure status; optional change history. Source: NTA Corporate Number System Web-API. Status: Implementation complete; awaiting issuance of the government API application ID (applied 2026-07-13, expected late July to late August 2026). Until connected, this tool returns UPSTREAM_UNAVAILABLE (HTTP 503) in production.",
      "tags": [
        "japan",
        "corporate",
        "corporate-number",
        "kyc",
        "verification"
      ],
      "examples": [
        "{\"skill\":\"verify_company\",\"params\":{\"corporate_number\":\"1180301018771\"}}"
      ],
      "inputModes": [
        "application/json"
      ],
      "outputModes": [
        "application/json"
      ]
    },
    {
      "id": "verify_invoice_number",
      "name": "Verify Qualified Invoice Issuer Registration",
      "description": "Check a qualified invoice issuer registration number (T + 13 digits) against the NTA Invoice Publication System: registration status, registration date, revocation/expiry; optional as-of-date validity and publication history. Confirmation-only by design: input is a registration number only \u2014 no name-based search, no reverse lookup, and no list/roster building (restricted by the data source's terms; publication data for sole proprietors is returned in the response only and never cached or stored). Source: NTA Qualified Invoice Issuer Publication System Web-API. Status: Implementation complete; the NTA Invoice Publication Web-API requires an approval-based review (applied 2026-07-12, expected mid to late August 2026). Until approved, this tool returns UPSTREAM_UNAVAILABLE (HTTP 503) in production.",
      "tags": [
        "japan",
        "invoice",
        "tax",
        "compliance",
        "verification"
      ],
      "examples": [
        "{\"skill\":\"verify_invoice_number\",\"params\":{\"registration_number\":\"T1180301018771\"}}"
      ],
      "inputModes": [
        "application/json"
      ],
      "outputModes": [
        "application/json"
      ]
    },
    {
      "id": "get_company_profile",
      "name": "Get Company Profile (gBizINFO)",
      "description": "Corporate profile for a 13-digit Japanese corporate number from gBizINFO REST API v2 (METI): address, representative, capital, employees and more, with per-field source and last-retrieved metadata. Status: Live (connected to gBizINFO REST API v2).",
      "tags": [
        "japan",
        "corporate",
        "gbizinfo",
        "company-profile",
        "open-data"
      ],
      "examples": [
        "{\"skill\":\"get_company_profile\",\"params\":{\"corporate_number\":\"1180301018771\"}}"
      ],
      "inputModes": [
        "application/json"
      ],
      "outputModes": [
        "application/json"
      ]
    },
    {
      "id": "normalize_address",
      "name": "Normalize Japanese Address",
      "description": "Normalize a Japanese address, decompose it to prefecture / municipality / town-aza level, resolve Address-Base-Registry town IDs, and cross-check the postal code (mismatches are reported, not silently fixed). v1 granularity: parsing stops at town/aza level \u2014 block/house numbers, lot numbers, koaza and Kyoto street names are returned as an unparsed remainder (no guessing). Sources: Digital Agency Address-Base-Registry + Japan Post postal-code data (bundled local masters). Status: Live (driven by bundled government master data; unaffected by government API outages).",
      "tags": [
        "japan",
        "address-normalization",
        "postal-code",
        "open-data"
      ],
      "examples": [
        "{\"skill\":\"normalize_address\",\"params\":{\"address\":\"\u6771\u4eac\u90fd\u5343\u4ee3\u7530\u533a\u971e\u304c\u95a21\u4e01\u76ee1-1\"}}"
      ],
      "inputModes": [
        "application/json"
      ],
      "outputModes": [
        "application/json"
      ]
    },
    {
      "id": "jp_calendar",
      "name": "Japanese Holidays and Business Days",
      "description": "Japanese national holiday lookup and business-day calculations (Cabinet Office national holiday CSV): is-business-day checks, adding business days, counting business days in a range; optional year-end (Dec 29 - Jan 3) handling. Status: Live (driven by bundled government master data; unaffected by government API outages).",
      "tags": [
        "japan",
        "holidays",
        "business-days",
        "calendar"
      ],
      "examples": [
        "{\"skill\":\"jp_calendar\",\"params\":{\"op\":\"is_business_day\",\"date\":\"2026-01-01\"}}"
      ],
      "inputModes": [
        "application/json"
      ],
      "outputModes": [
        "application/json"
      ]
    }
  ]
}