Taxi / PHV licensing workflow

Check a taxi or PHV licensing preflight

Choose one supported authority and provide structured applicant facts before a driver or private-hire licensing submission. This is preflight information, not licensing-authority approval or legal advice.

What this check does

  1. Checks whether the authority and structured facts are sufficient for the one-authority preflight.
  2. Shows a bounded readiness explanation and preserves UNKNOWN, REVIEW, and evidence-fail-closed behavior.
  3. Offers a separate checkout-intent step for an evidence-linked report. No payment details are collected.

No names, addresses, contact details, incident narratives, or payment credentials are requested.

Example licensing report

This synthetic example shows the current response shape. It is not a decision about your case.

authority
City of Bradford Metropolitan District Council
licensing path
Single-authority driver preflight
status
OK / review may still be required
evidence
Official-source basis and freshness-gate status
blockers
Blocking requirements when the engine evaluates them
missing information
Inputs evaluated as UNKNOWN
next step
Evidence-gated next action, not licensing approval

Start with structured facts

Only inputs already supported by the canonical Taxi/PHV engine are used. Vehicle/operator comparison and cross-authority comparison remain separate machine workflows.

Structured applicant facts

Leave optional facts blank when unknown. Unknown or conflicting evidence remains review-required.

The existing MCP/x402 machine path and prices remain available; the human-report price is confirmed before payment.