---
title: "Cross-border transfer preflight: one call returns ALLOW / ALLOW_PUBLIC_SIGNAL_ONLY / REVIEW / BLOCK with adequacy status, risk level and SCC requirement."
method: POST
path: "/v2/nomos/preflight"
tags: ["cross-border"]
---

# Cross-border transfer preflight: one call returns ALLOW / ALLOW_PUBLIC_SIGNAL_ONLY / REVIEW / BLOCK with adequacy status, risk level and SCC requirement.

`POST /v2/nomos/preflight`

AgentNOMOS Cross-Border Regulatory Compliance Preflight. Checks a planned cross-border data transfer between EU, India, Japan, Korea, Singapore and China against GDPR, DPDP, PIPL, FSA and MAS. Returns one verdict for the request (ALLOW, ALLOW_PUBLIC_SIGNAL_ONLY, REVIEW or BLOCK) inside `preflight_summary`, together with adequacy_status, risk_level, sccs_required, requires_human_review, blocked_fields and evidence_hash, plus scanned target candidates and a SHA-256 receipt_hash. Target-specific fields are withheld automatically when the verdict does not permit them. Classification only, not legal advice.

## Request body

- object
  - `source_regime` string — Origin regime of the data transfer. Auto-detected from `intent` when omitted.
  - `target_regime` string — Destination regime. Auto-detected from `intent` when omitted.
  - `region` string — Target-scan region filter. Derived from source_regime when omitted.
  - `data_category` string — Category of the data to be transferred. Drives the verdict; personal and payment categories resolve to BLOCK.
  - `query` string — Free-text target search query.
  - `intent` string — Free-text intent; used to auto-detect regimes, capability and data category when the explicit fields are absent.
  - `max_results` integer — Maximum scanned targets returned.
  - `min_score` integer — Minimum target score for a candidate to be included.

## Response `200`

Success (synthetic example)

## Other responses

- `400` — Bad Request — invalid or missing parameters.
- `402` — Payment Required (x402 v2): payment requirements are in the PAYMENT-REQUIRED response header (accepts[]); retry with the PAYMENT-SIGNATURE header (USDC on Base, eip155:8453). Success carries the PAYMENT-RESPONSE settlement header. The legacy X-PAYMENT header is not accepted on /v2 routes.

## Changes

- **2026-07-31** `8d0e6117ed88` — 1 breaking, 2 info
  - the `max_results` request property type/format changed from `number`/`` to `integer`/``
  - added the new optional request property `intent`
  - added the new optional request property `min_score`

[Change history](https://skmtc.dev/tooloracle/apis/tooloracle-mcp-platform/changes/v2/nomos/preflight/post.md)

---

[API](https://skmtc.dev/tooloracle/apis/tooloracle-mcp-platform.md) · [All operations](https://skmtc.dev/tooloracle/apis/tooloracle-mcp-platform/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/tooloracle/tooloracle-mcp-platform/revisions/854e280742bb/schema)