Organize public identity clues into human context that is traceable, auditable, and callable by agents
Users can create identity resolution projects based on public web page evidence, generate interpretable digital identity graphs, detect life event signals, and publish authenticated LLM-Ready JSON context interfaces for Agent calls.
- 01Source governanceConfigure open source scope, regional compliance policies, and identity seeds to form an auditable open source evidence base.
- 02Identity resolutionSplice public identity fragments into interpretable person_id and identity graph nodes.
- 03Event contextualizationDetect evidence-supported life event signals based on identity graphs and form contextual summaries.
- 04API contract reviewGenerate and review JSON API specifications, authentication rules and origin tracing policies for Agent calls.
Context API contract
Results, sources, failures, approvals, and rollbacks are saved by project.
No business results yet
There are no public source records. Please fill in the allowed data source domain name and identity seed first.
Data use boundary
Please only submit publicly identified torrents and publicly available source ranges that you have permission to process. The system will save public source URLs, collection time, identity fragments, evidence references, confidence levels, review status, and deletion/blocking records; do not submit ID numbers, bank card numbers, medical records, undisclosed contact information, account passwords, or login data. Current 10 Role Review Supplement: Identity seeds and free text input must be subject to sensitive information detection, rejection, or desensitization. ; Each project must record the minimum necessary set of fields corresponding to business_goal. By default, irrelevant personal fields are not collected or output. ;Removal/blocking must cascade to affect API, exports, reports, dashboard, subsequent actions, cache and rollback snapshots. ; Audit logs retain only the minimum metadata required for compliance, and limit access rights and retention periods. ;Public source records must contain the source URL, acquisition time, task ID, visibility/access policy checks, and failure/skip reasons.
Data retention
Project data is retained for 180 days by default; users can delete or block person_id and its associated profile, field, and event in advance. After deletion/blocking, the context API of this site will no longer return the identity and events, but the audit log can retain necessary operation records in accordance with compliance requirements.
Human responsibility and rollback
This product processes person-related clues, identity splicing, and life event signals in public web pages, which may create false associations, outdated information, bias, or privacy compliance risks. The output is only used for authorized business context analysis and Agent development testing, and may not be used as the sole basis for high-impact decisions such as credit, insurance, employment, housing, medical care, and legal enforcement.
Rollback only withdraws the source records, identity splicing reports, event signals, API contract versions and workflow status generated within this site; since the product is not connected to external production systems, rollback does not mean that any external CRM, advertising platform, data warehouse or third-party system has been modified or restored.