Código 07 · Human verification in Peru

Hire a human verifier (pay with x402)

solicitar_verificacion

Books a vetted human verifier from the Código 07 network in Peru to check something in the physical world. The first available verifier accepts it and delivers a report with geotagged photos. Standard services are paid instantly and confirmed with no human approval. Payment: x402 v2 (v1 compatible), USDC on Base. Call once without payment to receive a PaymentRequired (isError=true, structuredContent). Retry the SAME call adding params._meta["x402/payment"] with the signed PaymentPayload. When it settles, the task is confirmed instantly with no human approval, and the result includes _meta["x402/payment-response"]. Returns id + token_consulta; store both. servicio "personalizado" (or an on-site visit outside Lima) creates a free quote request instead; pay it later with pagar_solicitud. Prohibited requests (surveillance of private individuals, entering private property, handling money/packages, impersonation, anything illegal) are rejected automatically before any charge.

Input Schema

TableJSON Schema

Name	Required	Description
`ruc`	No	Peruvian company tax ID (RUC, 11 digits), if relevant.
`agente`	No	Name/identifier of your agent.
`urgente`	No	Rush job (+50%, half the turnaround).
`servicio`	Yes	verificacion_remota = USD 25, 24 h (phone call in Spanish + SUNAT/RUC lookup + web check, anywhere in Peru). visita_presencial_lima = USD 75, 48 h (on-site visit in Metropolitan Lima/Callao, 6+ geotagged photos). personalizado = free quote request for anything else (e.g. visits outside Lima), paid later with pagar_solicitud.
`ubicacion`	No	Full address and district (for on-site visits) or city.
`webhook_url`	No	Optional https URL. Receives POST updates (cotizada, completada, cancelada) signed with X-Codigo07-Signature = sha256 HMAC of the raw body using your token_consulta.
`que_verificar`	Yes	What exactly must be verified, in Spanish or English. Be specific: the question to answer and why.
`contacto_email`	No	Optional. Inbox where status updates can be sent.
`acepta_terminos`	Yes	Must be true: you accept the terms and limits at https://codigo07.vercel.app/#terminos.
`contacto_whatsapp`	No	Optional WhatsApp number with country code.
`entregable_esperado`	No	What you expect back (e.g. "6 photos of storefront + yes/no on whether it is open").

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 3, 2026

addedInput schema / properties / webhook_url

Added value: +{
+  "description": "Optional https URL. Receives POST updates (cotizada, completada, cancelada) signed with X-Codigo07-Signature = sha256 HMAC of the raw body using your token_consulta.",
+  "format": "uri",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only supply safety hints (readOnly=false, openWorld=true, idempotent=false); the description adds substantial context beyond them: the x402 payment handshake, instant no-human-approval settlement, what the result contains (_meta['x402/payment-response']), the need to store id and token_consulta, and the prohibited-request filtering that happens before any charge.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose and payment flow, and nearly every sentence carries operational weight. There is some mild redundancy ('confirmed with no human approval' is stated twice) and one long run-on sentence listing prohibited requests, but density is justified by the complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter async payment tool with no output schema, the description covers the call flow, error mode (isError=true, structuredContent), settlement behavior, returned identifiers, and webhook triggers. It is nearly complete; only the exact content of the delivered report beyond 'geotagged photos' is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema cannot: it explains the hidden runtime parameter params._meta['x402/payment'] that is not in the schema (additionalProperties: false), and clarifies the special behavior of servicio='personalizado'. The other parameters gain no extra semantics from the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Books a vetted human verifier from the Código 07 network in Peru') plus the concrete deliverable (report with geotagged photos). It also distinguishes itself from the quote path and from sibling pagar_solicitud, so an agent can identify the tool immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit two-step invocation instructions (call once to get PaymentRequired, retry the SAME call with params._meta['x402/payment']), names the alternative flow for 'personalizado'/out-of-Lima (free quote, pay later with pagar_solicitud), and lists conditions under which requests are auto-rejected before charge.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Código 07 · Human verification in Peru tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?