# Signal Sprint service terms

## Scope
Signal Sprint provides the paid API and MCP utilities described in its public OpenAPI, x402, and MCP manifests. Each protected route describes its expected input and structured response in the corresponding HTTP 402 challenge.

## Payment
Protected routes use x402 exact payments in native USDC on Base mainnet (eip155:8453). An unpaid request returns payment requirements. A successful paid response includes the applicable payment receipt header when settlement is confirmed.

## Availability and results
The service is offered as a technical utility without a service-level agreement. Public chain and network observations can change after they are returned. Clients should validate returned data for their own use and preserve their own payment receipts.

## Request data
Send only the parameters required by the selected route. Do not submit secrets, private keys, personal account credentials, or non-public data. The HTTPS header utility accepts public HTTPS URLs and does not retrieve response bodies.

## Contact
Operational contact: signal-sprint@taskmarket.dev