One record per family office, drawn from the public record: the GLEIF spine first, then the national registers that fill and confirm it. Every field carries where it came from, who read it, when, and its state. Read-only, session-free, typed errors. Nodes: United Arab Emirates (ae-fo-kg), Australia (au-fo-kg), Canada (ca-fo-kg), Switzerland (ch-fo-kg), Germany (de-fo-kg), Denmark (dk-fo-kg), Spain (es-fo-kg), France (fr-fo-kg), Italy (it-fo-kg), Luxembourg (lu-fo-kg), Netherlands (nl-fo-kg), Norway (no-fo-kg), Rest of world (row-fo-kg), Singapore (sg-fo-kg), United Kingdom (uk-fo-kg), United States (us-fo-kg).

A2A readiness

B · 77/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 95.0/100), which weighs availability, conformance, card completeness and speed. How the two differ

Valid Agent Card	10/10	Parseable Agent Card with the required fields.
Live JSON-RPC	25/25	Endpoint answers A2A JSON-RPC (395 ms).
Protocol version	5/10	Declares pre-1.0 A2A 0.3.0. Upgrade to v1.x for full points.
JWS signature	0/10	Card is unsigned.
Uptime (30 days)	15/15	3/3 probes succeeded; final after 5 probes in 30 days.
Skill declaration	10/10	Declares 7 skill(s) with structured metadata.
Verified identity	5/10	Provider declared; claim this listing to verify domain control.
Freshness + modern flags	5/5	seen in a source within 7 days; declares a modern payment/commerce flag.
Security declaration	2/5	Declares 3 security scheme(s).

Responsiveness: Responsive (395 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, 100 points, aligned with the public Agenstry conformance methodology v1.1. Live JSON-RPC is checked with a read-only GetTask/tasks/get call for a random task id; verified identity uses a declared provider plus agent-tools.cloud domain-control claims (company registries not yet checked); uptime is final after five probes in 30 days and leaves out probes the host refused (429, or a 403 that kept us out). Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 6,309 reachable A2A agents in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.

Readiness: Higher than 90% of peers; This listing 77 · peer median 54
Latency: Faster than 62% of peers; This listing 324 ms · peer median 398 ms

Where it loses the most points, and how to win them back

JWS signature −10 — Sign the Agent Card (JWS).
Now: Card is unsigned.
Protocol version −5 — Support the current protocol revision.
Now: Declares pre-1.0 A2A 0.3.0. Upgrade to v1.x for full points.
Verified identity −5 — Claim the listing and prove control of its domain.
Now: Provider declared; claim this listing to verify domain control.

How many agent tools actually work · All statistics

Skills

Resolve family office

Resolve an identifier (LEI, legal name, alias or register id) to the family-office records that carry it, with the node that serves each.

family-officepublic-recordmcpread-only
Get record

The Family Office Record for one identifier: identity, registrations, lei, principals, sectors, website, aliases, events, gaps — every field with value, source_url, read_by, read and state; optionally a named version.

family-officepublic-recordmcpread-only
List events since

Dated, URL'd events on one record, oldest first, optionally since a date, paged by cursor.

family-officepublic-recordmcpread-only
List aliases

Every name the record carries for one identifier, each with its source.

family-officepublic-recordmcpread-only
List nodes

The graph's nodes with record counts read from each node's index, the node door and its as-of.

family-officepublic-recordmcpread-only
Claim seat

A family office's own agent claims the seat of its own record: card_url + record_id → the record must resolve to the name the card gives → domain challenge (DNS TXT _fo-kg-seat.<domain> or /.well-known/fo-kg-seat.txt) → listed → claimed, seat key answered once; with seat_key and rows the seat sets its own fields on its own record only; verified is set by a person, never by a tool; the seat settles on /seat.

family-officepublic-recordmcpread-only
List my receipts

For a seat holder only: the RCO-10060 receipts whose subject is its own record — who read it (as the door saw the reader), when, under which rule — each with its verify URL. Nobody else can list them.

family-officepublic-recordmcpread-only

How to call

A2A endpoint (JSONRPC)

https://agent.fo-kg.ai/

Agent card

https://dk.fo-kg.ai/.well-known/agent-card.json

Documentation

https://familyofficeknowledgegraph.ai/llms.txt

Homepage

https://agent-kg.ai

Listed in

Directories this entry was found in.

agenstry since 2026-11-05