Run these checks in order so failures stay isolated and easy to diagnose.
# 1. Direct adapter check
curl -X POST https://api.decionis.com/v1/google-cloud/vertex/extensions/verify \
-H "Authorization: Bearer dcy_org_xxx" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: vertex-go-live-1" \
-d '{
"org_id": "<org_uuid>",
"decision_type": "TRANSACTION_ROUTING",
"workflow_key": "finance_transaction_routing",
"system_of_record": "SAP",
"intent": {
"action_type": "CREATE_VENDOR_PAYMENT",
"target_entity": "invoice",
"target_id": "INV-2048",
"payload": {
"invoice_id": "INV-2048",
"currency": "EUR"
}
},
"google_context": {
"project_id": "your-gcp-project",
"location": "europe-west1",
"agent_id": "vertex-agent-1"
}
}'
# 2. Inspect the response for:
# status
# policy_version
# verification
# google_identity_verified
# regional_posture
# metering
# metering_export
# execution_guidance
# 3. Replay the same request with the same Idempotency-Key
# Expect stable governed output, not a second uncontrolled action
# 4. List recorded Vertex metering events
curl -H "Authorization: Bearer dcy_org_xxx" \
https://api.decionis.com/v1/orgs/<org_id>/google-cloud/vertex/metering
# 5. If Service Control export is enabled and a prior export failed,
# replay the export without rerunning the business decision
curl -X POST -H "Authorization: Bearer dcy_org_xxx" \
https://api.decionis.com/v1/orgs/<org_id>/google-cloud/vertex/metering/<event_id>/replay-service-control
| Check | Expected result |
|---|
| Direct adapter call | HTTP 200 with a governed verdict and dossier proof. |
| Idempotent replay | Same outcome with replay-safe behavior. |
| Dossier verification | Public verification URL resolves cleanly. |
| Execution gating | Downstream step only runs when execution_guidance.allowed is true. |
| Metering ledger | A verified_decision event exists for the call. |