OPERATIONAL RUNBOOK

This runbook helps you operate the Neura API integration in production. It focuses on payment continuity, monitoring, and incident response from a client perspective.

Payment management

• Wallet funding: Keep sufficient balances on both Solana and Base wallets to cover request volume and network fees. Automate top ups when balances fall below configured thresholds.

• Invoice caching: Avoid replaying expired invoices. Cache invoice payloads with short expirations (for example 60 seconds) and request fresh invoices when stale.

• Key rotation: Rotate CDP_API_KEY_SECRET periodically. Update all automation scripts immediately after rotation to prevent facilitator authentication failures.

Monitoring

Signal	Recommended action
success: false responses	Capture the error message and route to logs or alerts.
status=429	Track frequency. If spikes occur, increase client backoff and evaluate request batching.
status=402 without successful replay	Investigate payment proof generation.
Latency > baseline	Check network congestion, especially when switching between Solana and Base.
/health/resilience remaining points nearing zero	Slow down request rate or distribute load across additional clients.

Integrate these metrics into your observability stack (Datadog, Grafana, Prometheus, etc.).

Alerting thresholds

• Error rate: Alert when more than 1 percent of requests within a five minute window contain success: false.

• Payment failures: Alert when two consecutive payment attempts for the same invoice fail.

• Wallet balance: Alert when the balance drops below two hours of expected usage.

Incident response

1. Capture context: Request path, timestamp, invoice hash, and payment transaction hash.

2. Check status pages: Monitor Neura and Coinbase status dashboards for known incidents.

3. Retry with backoff: For transient 5xx responses, retry with exponential backoff (start at 5 seconds, double up to 60 seconds).

4. Escalate: Contact Neura support with logs and transaction references if failures persist beyond three retries.

Change management

• Test new releases of the Coinbase X402 SDKs in a staging environment before production rollout.

• Maintain compatibility tests for each critical endpoint (see Testing Playbook).

• Document all environment variable changes and wallet rotations in your change log.

Security practices

• Store CDP_API_KEY_SECRET in a secret manager (AWS Secrets Manager, GCP Secret Manager, HashiCorp Vault, etc.).

• Limit access to payment wallets. Use hardware wallets or custodial solutions for production funds.

• Audit API usage regularly to confirm it aligns with expected volume.

Support

• Primary channel: Contact your Neura account team or support alias.

• Required information: Include timestamps, endpoint paths, invoice payloads, settlement transaction hashes, and relevant error messages.

• Expected response: Neura acknowledges incidents within standard SLA terms defined in your contract.