Coming soon. We aren’t taking orders yet.

By vertical

Background checks for kids and learning marketplaces

Parents trust you with their kids. Check every tutor, coach and camp counselor before the first session.

Who gets checked

Anyone who works with children through your marketplace.

In person or online, paid or volunteer, everyone a parent books through you gets the same check before their first session.

Kids and learning

Who gets checked

  • Tutors, in person and online
  • Coaches and sports instructors
  • Camp staff and counselors
  • Music, art and language teachers

Checks for kids and learning

The core check on every provider, with the sex offender registry on every report.

Live ID verification comes first, so every search runs on the right person. A named analyst matches every possible record to the provider and confirms it at the court before signing the report. State abuse registries and ongoing monitoring are coming.

  • Live ID verificationID photo and a live selfie, on the provider’s phone.Included
  • Identity and address historyNames and addresses, which decide where to search.Included
  • National criminal database searchA wide first pass. Matches are checked against the person and confirmed at the court.Included
  • County criminal recordsThe court in every county lived in over the last 7 years.Included
  • Sex offender registryEvery state’s public registry.Included
  • Global watchlistGovernment sanctions and watch lists, by name.Included
  • Abuse registriesState child abuse and neglect registries.Coming
  • Ongoing monitoringAn alert when a new record is filed after onboarding.Coming

State rules for people who work with kids

Many states set their own checks for people who work with minors.

Pennsylvania, California and New York, among others, have rules for people who work with children, and some reach volunteers and contractors too. Your team decides which rules apply to your marketplace.

Roster prepares the state notice for the provider’s state, and the pre-adverse and adverse letters with the dates filled in. Your team sends them and makes the call. Care marketplaces share most of these rules: see the care playbook.

Examples, among others: Pennsylvania, California and New York.

An example onboarding flow

From sign-up to a signed report, with your app kept up to date.

  1. A tutor signs up and your app calls POST /v1/checks.
  2. They sign consent and confirm their identity with their ID and a live selfie, on their phone, in your brand.
  3. Webhooks tell your app when each search moves and when the report is signed.
  4. If something shows up, the notices and letters are prepared for your team to send. A person on your team approves any adverse action.
  1. Your appSign-upPOST /v1/checks
  2. Their phoneConsent and live IDIn your brand
  3. As it runsCourt searchesWebhooks
  4. When doneSigned reportPage and PDF
  5. PreparedNotices if neededYour team sends

When a check waits on a court

Tell the tutor why, in one plain sentence.

Some county courts don’t put their records online, so a check can wait while someone searches at the courthouse. Waiting doesn’t mean anything was found.

explain_status returns a sentence your app or agent can pass straight to the provider: their first name, the court and a rough time. For the longer answer, link them to why a check waits on a county court.

Request

explain_status({ check: "chk_4Tn7" })

Response200 OK

Your check is waiting on Hamilton County court.
That usually takes one more business day.

Monitoring is coming

Ongoing checks after onboarding are on the way.

Ongoing monitoring isn’t live yet. When it is, a webhook will tell you when a new record turns up for a provider who has already passed their check, and your team will review it and decide. Abuse registries come with it.

Run a test tutor check in the sandbox.

Sandbox keys right away, no sales call. Live keys after a short credentialing call.

  • One call starts a check. Hosted consent and live ID in your brand; a webhook when it’s done. Sandbox keys without a sales call.
  • Status by API, webhook and MCP. explain_status says which court it’s waiting on and when to expect it.
  • A named analyst matches every possible record to the provider and confirms it at the court before it’s reported. A signed report page and PDF your team can open.
  • Every notice and letter prepared, with the waiting-period dates filled in, and a human approval gate before adverse action.
  • You send the notices and make the final call. Contractors covered the same way as employees.

Reviewed November 6, 2026 by Ben Drellishak, Owner. Markdown version.