Entity enrichment

Company name → verified identity + web footprint dossier: Wikidata facts, the official LEI legal-entity record, the SEC EDGAR filer, domain registration, tech stack, and brand favicon - in one pass.

When to use this pack

KYB, lead enrichment, or counterparty checks - an agent has a company name (maybe a domain and ticker) and needs to establish that the entity is real, who it legally is, and what its web presence looks like.

Tools in this pack

All 6 run inside the single $0.022 call above. Each is also callable on its own if you only need one part.

• Wikidata entity facts POST /api/wikidata-entity Company/person/organization facts from Wikidata. Pass an entity id (e.g. Q312 for Apple Inc.) for the enrichment record - label, description, aliases, and a curated fact set (inception, HQ location, country, industry, founders, CEO, employees, revenue, official website, LEI, ticker + exchange, ISIN, logo; for people: birth/death dates, citizenship, occupation) with item references resolved to human-readable labels. Or pass a name to search: ambiguous names return ranked candidate matches in Wikidata's stable order. Keyless.
• Legal entity (LEI) lookup POST /api/lei-lookup Look up a legal entity in the official GLEIF registry. Pass a 20-character LEI for the full record - legal name, jurisdiction, legal form, addresses, registration status, and the reported direct + ultimate parent entities - or pass a company name to fulltext-search the registry and get ranked candidate LEIs. Unknown LEIs return {found:false}; parents that aren't reported return null. Official registry data, keyless.
• EDGAR company lookup (ticker → CIK) GET /api/edgar-company-lookup Resolve a US stock ticker (e.g. AAPL) to its SEC CIK number, the primitive every other EDGAR call needs. Returns ticker, cik (zero-padded, 0000320193), cikInt (320193) and the registered company name. Backed by SEC's company_tickers.json (public domain). A company name sent where the ticker goes is answered with a 404 that names the likely tickers ("Tesla" -> TSLA). ?ticker=AAPL
• Domain WHOIS (RDAP) POST /api/whois Domain registration data via RDAP (the structured WHOIS successor): registrar, creation/expiry dates, status, nameservers.
• Tech stack detection POST /api/tech-stack Detect the technology stack of a public website: CDN, web server, language/runtime, frontend framework (Next.js, Nuxt, SvelteKit, Remix, Astro, React, Vue, Angular), CMS (WordPress, Drupal, Ghost, Shopify, Wix, Squarespace, Webflow), analytics (GA, GTM, PostHog, Mixpanel, Segment, Hotjar, Plausible, Fathom), and payments (Stripe, PayPal). Signature-based; no third-party API.
• Site favicon grabber POST /api/favicon-grab Fetch a site's favicon/logo: reads the page's declared <link rel=icon…> tags (all variants with their sizes and types), deterministically picks the largest declared icon (falling back to /favicon.ico), fetches it, and returns the bytes as a base64 data URI plus the resolved icon URL and content type. Icons over 256KB return the URL and metadata without the inline data URI. SSRF-guarded - private-network hosts are rejected. Sites with no reachable icon return {found:false}.

Bought one at a time, these 6 tools cost $0.024 together; the pack is that sum less a 10% bundle discount, rounded up to the $0.001 settlement floor, which is $0.022.

Workflow

1. Resolve the name to a Wikidata entity with wikidata-entity - the encyclopedic identity: what it is, founding date, headquarters, official website.
2. Look up the Legal Entity Identifier record with lei-lookup (GLEIF) - the verified legal name, jurisdiction, and registered address.
3. Find the SEC EDGAR filer with edgar-company-lookup - CIK number and filing history existence (public companies only).
4. Pull domain registration with whois - creation date, registrar, and expiry; a week-old domain claiming a decades-old brand is a red flag.
5. Fingerprint the site's tech-stack - CMS, framework, CDN - the operational footprint.
6. Grab the favicon with favicon-grab as the brand asset for the dossier card.

Arguments

What one call returns

A JSON object with pack, args, steps, summary; steps holds one entry per tool (wikidata-entity, lei-lookup, edgar-company-lookup, whois, tech-stack, favicon-grab), each with its own result or error. Full example on the API page.

Call it directly

Any x402 client pays the 402 and gets the whole workflow back in one response. With the agent402-client SDK (npm i agent402-client, an ES module):

import { Agent402 } from "agent402-client";
// payFetch: an x402-wrapped fetch your wallet signs (@x402/fetch).
// Tools on the free tier need no options: new Agent402() pays them by proof-of-work.
// an existing prepaid credits key also works: new Agent402({ creditsKey })
const client = new Agent402({ fetch: payFetch });
const result = await client.call("skill-entity-enrich", {"name":"Apple","domain":"apple.com","ticker":"AAPL"});

Run it in Claude

claude mcp add agent402 -s user -- npx -y agent402-mcp@latest

Then paste this prompt into Claude:

Build an identity dossier on Apple (domain apple.com, ticker AAPL) using Agent402's entity-enrich skill pack. (1) Resolve the Wikidata entity, (2) look up the LEI legal-entity record, (3) find the SEC EDGAR filer, (4) pull whois on the domain, (5) fingerprint the tech stack, (6) grab the favicon. Report as a KYB-style dossier: verified legal identity, public-company status, domain age vs claimed history, and web footprint - flag any mismatches.

← All skill packs