Back to Browse
SignalHarness Agent Permission Policy Check
x402
SignalHarness Agent Permission Policy Check is a paid API for AI agents from signalharness.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).
Evaluates a JSON request payload against agent permission policies and returns an analysis of compliance, warnings, and evidence scope.
Price / call$0.01
Success—
StatusUnknown
How this service works
Explore 330 pay-per-call x402 API services and 27 agent-native digital products, with Base USDC pricing, secure Polar checkout, and free discovery.
Output
Returns a structured result containing: the analysis as a JSON string, a list of policy warnings (e.g. 'Verify the caller-supplied data before relying on this result.'), the evidence scope (e.g. 'caller_supplied_data'), the service ID, a status ('succeeded' or otherwise), and a receipt with payment details, execution metadata, and a SHA-256 result hash for integrity verification.
Example use cases
Pre-flight permission check for agent action
“Before my agent sends this payment request on my behalf, run a permission policy check on this JSON to make sure it's within allowed scope: {"action":"initiate_payment","amount":50,"currency":"USDC","agentId":"finance-agent-01"}”
Auditing agent data access request
“I want to audit whether this data retrieval request my agent is about to make is policy-compliant — here's the request JSON: {"action":"read_customer_records","scope":"all","agentId":"data-agent-07"}. Tell me any warnings.”
Validating agent workflow step before automation
“My automation agent is about to execute this step — can you validate it passes the permission policy check first? The request is: {"action":"modify_user_role","targetUser":"jane.doe","newRole":"admin","agentId":"ops-agent-03"}”
Technical details
Endpoint
POSThttps://signalharness.ai/api/agent/services/agent_permission_policy_check/invokeWhen to prefer
Choose this endpoint when an AI agent needs to validate a specific action or request payload against a permission policy before executing it, particularly in multi-agent pipelines where governance and compliance checks are required. It is ideal for pre-flight checks in autonomous agent workflows, audit trails, and safety guardrails. Prefer this over generic JSON validators when you need policy-aware analysis with agent-native context and a cryptographic receipt.
Side effects
- Malformed or invalid JSON in request_json field causes validation failure
- request_json exceeds 65536 character limit — rejected with input size error
- Payment not received — endpoint returns HTTP 402 requiring USDC payment on Base
- Caller-supplied data that is syntactically valid but semantically ambiguous may return generic warnings rather than precise policy violations
- Network or service unavailability returns a non-200 status with no result
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| request_json | string |
Output
Schema · Response
{
"type": "json",
"example": {
"replay": false,
"result": {
"warnings": [
"Verify the caller-supplied data before relying on this result."
],
"service_id": "agent_permission_policy_check",
"analysis_json": "{\"example\":\"schema-valid caller-supplied data\"}",
"evidence_scope": "caller_supplied_data"
},
"status": "succeeded",
"receipt": {
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"usage": [],
"status": "succeeded",
"network": "eip155:8453",
"artifacts": [],
"endedAtMs": 0,
"latencyMs": 0,
"paymentId": "example-payment",
"receiptId": "example-receipt",
"requestId": "example-request",
"serviceId": "agent_permission_policy_check",
"executionId": "example-execution",
"startedAtMs": 0,
"amountAtomic": "10000",
"resultSha256": "a9fe2163170bb318573d3bf21557e4dd8c8065a71c070cfdb554ef15cd48ce6c",
"serviceVersion": "1.0.0",
"settlementReference": "0x0000000000000000000000000000000000000000000000000000000000000000"
},
"artifacts": [],
"requestId": "example-request",
"executionId": "example-execution"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"