Partner API
Registered partners post structured objects to POST /api/hub/signals or POST /api/hub/opencrawl/updates. Reviewed by curators on the same queue as everything else.
The hub accepts a small list of safe object types. Anything that could identify a worker, employer, or case is refused at the schema gate before storage. If you have a case to report, please use the verified hotlines listed in the relevant pack instead.
All submissions go through curator review before they affect any pack, tool, or contact.
fee_request trend)Every submission is treated as untrusted text until the server-side PII detector clears it. Nothing is published automatically.
Submission must match one of the allowed object types. Free text outside declared fields is dropped.
The server-side PII detector scans every text field. If it triggers, the submission is rejected with a reason; nothing is stored.
Borderline submissions land in a quarantine queue, never the public store.
A human curator reviews accepted submissions and decides what they become: pack diff, tool proposal, contact update, eval candidate.
If a submission becomes a pack diff, it runs through the regression suite before anything is published.
The submitter receives a structured receipt with the review state. No identifying details about reviewers leave the hub.
No accounts. Three channels: API for partners, email for everyone, web form for one-off submissions.
Registered partners post structured objects to POST /api/hub/signals or POST /api/hub/opencrawl/updates. Reviewed by curators on the same queue as everything else.
Reply to a newsletter question, or write to submissions@duecare-ai.com. Replies pass through the server-side PII detector before any human or model reads structured fields.
One-off submissions through a lightweight form with strict object types. No free-text catch-all field exists.