ResolveSignal
Product/Integrate/Developer guide

Developer integration guide

Integrate without adding an LLM.

Your system supplies current structured evidence, pays for one bounded analysis, and receives one typed recommendation. Execution authority stays in your application.

Download Python kit ↓Machine-readable guide

01 / Integration contract

Keep one static profile in your repository. Build fresh runtime evidence for every call. Validate both locally before any wallet operation.

  1. 01

    Read the live contract

    Check service readiness and the authoritative form.

    GET /health · GET /v2/form
  2. 02

    Create a quote

    Submit complete, locally validated input and prove control of the payer.

    POST /v2/requests
  3. 03

    Pay once

    Accept only a matching x402 exact challenge within your explicit fee cap.

    POST /v2/requests/{call_id}/pay
  4. 04

    Validate the result

    Match call ID, input hash, payer and financial state before using the recommendation.

    typed response

Static profile

Reviewed configuration that changes deliberately.

  • Objective and policy
  • Available capabilities
  • Locale and operating boundaries
Open profile schema →

Runtime evidence

Fresh facts collected for this independent purchase.

  • Current state and observations
  • Facts and previous attempts
  • Observed timestamp
Open runtime schema →

03 / Payment boundary

Before payment

Reject missing, blank, stale, unknown or extra fields according to the live form. Check the exact amount and initialized vault from the quote.

After submission

Persist only recovery metadata. If the outcome is ambiguous, reconcile the same call. Never create an automatic second purchase.

Before execution

Map action IDs to allowlisted local handlers and re-check your system's authority and preconditions.

04 / Python reference

terminal

The reference package includes request building, local schema validation, x402 orchestration and recovery metadata.

python -m pip install https://resolvesignal.com/integration/resolvesignal-python.zip

resolvesignal build \
  --profile config/resolvesignal-profile.json \
  --runtime run/current-evidence.json \
  --output run/request.json

resolvesignal validate \
  --profile config/resolvesignal-profile.json \
  --runtime run/current-evidence.json

Build and validation are local and do not authorize a purchase.

05 / Release checklist

✓ Schemas pinned and validated locally✓ Fee cap enforced before wallet use✓ One payment attempt per call✓ Recovery metadata excludes business data✓ Returned identifiers cross-checked✓ Action handlers explicitly allowlisted

Direct resources

Use the HTML guide for reading. Use the direct files in automated tooling.

Markdown guide →Example profile →Example runtime →Live form →