Data for people

Public people and company facts: enrich a person, search people, or look up a company. There is nothing to connect. Access owns the vendor relationship; agents call Access-owned capabilities, never a vendor SKU.

This resource is platform-owned. It does not appear in Resources → New. On hosted installs it shows on the resource list as Data for people. The open-source binary stubs the catalog.

What agents can do

Call describe on data-for-people for the tool list and schemas. Then run a capability the same way as Gmail:

execute({resource:"data-for-people", operation:"people.enrich", input:{email:"alex@acme.com"}})

Capability ids are Access-owned (people.enrich, people.search, people.company). people.enrich takes an email or a LinkedIn URL. Unknown capabilities fail before any paid request.

Keep it safe

Read-only. Grant the resource on the agent. Cross-product calls fail closed.

Example

Enrich alex@acme.com and look up the company behind acme.com.