# OneShot Person Dossier Lookup > OneShot Person Dossier Lookup is a paid API for AI agents from win.oneshotagent.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-16). Returns a comprehensive person dossier including enriched profile, social accounts, articles, and posts given a name, email, company, or social URL. ## Facts - Endpoint: POST https://win.oneshotagent.com/v1/tools/lookup/person-dossier?utm_source=zero.xyz - Price: $0.001/call - Payment: x402 - Status: unknown - Last checked: 2026-10-16 - Activations on Zero: 0 - Tags: x402 - Canonical page: https://www.zero.xyz/c/oneshot-person-dossier-lookup-2fedbce2 - Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Yy4F2139t2ODUNuLWbby2 Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently. ## How to call it through Zero Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`): ```sh zero fetch --capability oneshot-person-dossier-lookup-2fedbce2 -d '' ``` Example prompt: Pull up a full dossier on Jane Doe at jane@example.com who works at Acme Corp — include her social accounts and articles, and also look up her phone number. ## When to prefer this Use this endpoint when you need a comprehensive, multi-dimensional person profile in a single call — combining professional enrichment (title, company, email), social account discovery, articles, and posts. Prefer this over narrower sibling endpoints (like the social posts or social interactions endpoints) when you want a full dossier rather than a single data type. Best suited for sales intelligence, pre-meeting research, lead enrichment, or background due diligence on individuals. ## Known failure modes - Person not found — profile state returns 'unavailable' with empty data - No phone number available even with include_phone=true — phone field is null, not guaranteed - Insufficient identifying information provided — lookup may return partial results - Rate limiting or payment failure via x402 — 402 returned if payment signature is missing or invalid - Async delay — initial call returns 202 with request_id; result must be polled via GET /v1/requests/{id} ## How this service works Tools, payments, and compute orchestration for autonomous AI agents. ## Authentication - **`x402Payment`** — paid tool endpoints use the [x402 payment protocol](https://x402.io). First call returns `402 Payment Required` with a quote; sign and resend the request with `payment-signature: ` and `X-Quote-ID: `. - **`agentId`** — free read-only endpoints accept `X-Agent-ID: ` (0x… address). - **`soulKey`** — soul marketplace seller dashboard uses `Authorization: Bearer soul_…` (issued by `POST /v1/soul/register`). - **`acpBearer`** — Stripe ACP checkout sessions use a separate bearer token plus the `API-Version: 2026-01-30` header. ## Async tools & polling Most tool endpoints return `202 Accepted` with `{ request_id, tool, status }`. Poll `GET /v1/requests/{id}` (with the same `X-Agent-ID`) to retrieve the final result. A WebSocket fallback is available at `wss:///v1/requests/subscribe`. ## Pricing See [docs.oneshotagent.com/pricing](https://docs.oneshotagent.com/pricing) for the full table. Per-call prices for this environment: | Tool | Cost | |---|---| | Web search | $0.001 | | Web read | $0.002 | | Research | $0.01 | | Person profile | $0.005 | | Person email status | $0.001 | | Person dossier | $0.10 | | Person social accounts | $0.50 | | Business search | $0.01 | | Commerce search | $0.002 | | LinkedIn history sync | $0.02 per bounded run | | LinkedIn reply | $0.02 per message | | LinkedIn message to a connection | $0.02 per message | | LinkedIn profile view | $0.01 per view | | LinkedIn post reaction | $0.01 per reaction | | Email send | quote-based; service fee from $0.005 per send | | SMS send | $0.0035 per segment per recipient | | Voice call | $0.35/minute + $5.00 number registration on the first call | | Browser task | quote-based; minimum $0.005 | | Website build | quote-based; from $1.00 | | Compute goal | quote-based; minimum budget $1.00 + 20% platform fee | ## Error format `{ "error": "", "message": "", "details": }`. Validation errors include a `details` field with the failing field paths. ## Output A JSON object with a `result` containing: a `profile` section (name, email, phone, title, company, location, LinkedIn URL, company domain, social accounts), a `social_accounts` section, an `articles` section, a `posts` section, and a plain-English `summary` of what was found. Each section includes a `state` field (found/unavailable/none) and a `data` array. Also returns `status`, `request_id`, and `completed_at`. ## Request schema (JSON Schema) ```json { "type": "object", "properties": { "name": { "type": "string", "description": "Full name" }, "email": { "type": "string", "format": "email", "description": "Email address" }, "phone": { "type": "string", "description": "Phone number" }, "company": { "type": "string", "description": "Employer name or domain, e.g. \"Coinbase\" or \"coinbase.com\"" }, "profile_url": { "type": "string", "format": "uri", "description": "Profile URL on LinkedIn, X or GitHub" }, "linkedin_url": { "type": "string", "format": "uri", "description": "Same as profile_url (older name)" }, "include_phone": { "type": "boolean", "default": false, "description": "Phone lookup is off by default. include_phone=true adds the per-person add-on on the pricing page for up to one person; no phone hit is guaranteed." }, "social_media_url": { "type": "string", "format": "uri", "description": "Same as profile_url (older name)" } } } ``` ## Response schema (JSON Schema) ```json { "type": "json", "example": { "result": { "posts": { "data": [], "state": "unavailable" }, "profile": { "data": { "email": "jane@example.com", "phone": null, "title": "Engineer", "company": "Example", "summary": null, "location": null, "full_name": "Jane Doe", "last_name": "Doe", "first_name": "Jane", "linkedin_url": null, "company_domain": "example.com", "social_accounts": [] }, "state": "found" }, "summary": "Only the profile was found; no additional account, article or post content was found.", "articles": { "data": [], "state": "none" }, "social_accounts": { "data": [], "state": "none" } }, "status": "completed", "request_id": "uuid", "completed_at": "2026-10-14T10:00:00Z" } } ``` ## More - Live health (JSON, refreshed every minute): https://www.zero.xyz/c/oneshot-person-dossier-lookup-2fedbce2/health.json - [Zero catalog index](https://www.zero.xyz/llms.txt) - [Other services from win.oneshotagent.com](https://www.zero.xyz/host/win.oneshotagent.com/llms.txt)