Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory

People Data Labs

Paid API · mpp.orthogonal.com · found in a public registry · checked since 2026-10-18

Live, payment required · latest check

As JSON

GET https://mpp.orthogonal.com/peopledatalabs/v5/person/identifyNo per-call price known

The name is the registry's label, not ours. Not reviewed by a person. See 850 endpoints from orthogonal.com.

Our checks

An unpaid request daily, from eastern North America

Last 1 checks, oldest to newest; room for 29 more

1 passed, 0 failed, 29 not run.

Passed, 30 daysshort history1 of 1 run
Checks missed0in 30 days
Response, latest4669 msto first headers
Scheduledailyset by usage; rule below
Checked since2026-10-18under 1 day
Freshnessfreshagainst its schedule

Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.

Details

Payment terms

Price per call
—
Protocols
mpp
Networks
tempo:4217
Terms changes, 90 days
no valid payment request yet

Price from the registry's payment terms; protocols and networks from its payment request at our checks. Definitions

Access

Our latest check
Asked for payment (MPP)
Stated
not stated
Payment model
Per call (asked for payment for our request)

"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions

Listing

In the capability tree: Search and information / Companies and people / Find people and profiles (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-18. Wrong place? Tell us.

In the directory: meets our listing criteria (listing-criteria/3): ✓ says what it does; ✓ its latest check passed; ✗ fewer than 5 payers in 30 days (registry figure); ✓ listed in a curated catalogue (counts in place of the payer figure).

Purpose tags: none in the registry

Recent probes

WhenResultNetworks offeredTime to headers

cloudflare:EWR
Live, valid payment request HTTP 402 tempo:4217 4669 ms

What these figures do not show

  • A passing probe means the endpoint answered an unpaid request with a valid payment request on a production network (x402 on a mainnet network, or MPP on Tempo mainnet). It does not show that a paid call succeeds or returns useful results.
  • Payer and call counts are the registry's own figures, not our measurements.
  • The registry's description is not republished.
  • Limited evidence: monitored for under 1 day (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_81339c1e9b9752be