Hi maintainers -- Pact Network (pactnetwork.io) is a Solana on-chain coverage and refund layer for agent API calls. It is complementary to pay rather than a payment-gated API itself: an agent's pay CLI pays the merchant directly, and Pact side-wraps that call to debit a small premium and auto-refund on an SLA breach (latency, 5xx, network error), settled on-chain.
Mechanically, Pact charges via a pre-authorized SPL Token delegation that is debited on-chain in batches (settle_batch); it does NOT issue an HTTP 402 / x402 / MPP per-call payment challenge, so it is not a probeable providers/ entry and we are deliberately not opening one.
We do operate an insured proxy (market.pactnetwork.io) that wraps curated upstreams, and it publishes a public machine-readable endpoint catalog at market.pactnetwork.io/.well-known/endpoints (slug, hostnames, premium bps, paused).
Question: what is the right listing form for a pay-COMPANION coverage layer like this -- an aggregators/ entry pointing at our catalog, a README "related tools" mention, or a new section for pay-companion tooling? We want to be listed honestly and will follow whatever shape you prefer. Happy to open the corresponding PR once you confirm the form.
References:
Hi maintainers -- Pact Network (pactnetwork.io) is a Solana on-chain coverage and refund layer for agent API calls. It is complementary to pay rather than a payment-gated API itself: an agent's pay CLI pays the merchant directly, and Pact side-wraps that call to debit a small premium and auto-refund on an SLA breach (latency, 5xx, network error), settled on-chain.
Mechanically, Pact charges via a pre-authorized SPL Token delegation that is debited on-chain in batches (settle_batch); it does NOT issue an HTTP 402 / x402 / MPP per-call payment challenge, so it is not a probeable providers/ entry and we are deliberately not opening one.
We do operate an insured proxy (market.pactnetwork.io) that wraps curated upstreams, and it publishes a public machine-readable endpoint catalog at market.pactnetwork.io/.well-known/endpoints (slug, hostnames, premium bps, paused).
Question: what is the right listing form for a pay-COMPANION coverage layer like this -- an aggregators/ entry pointing at our catalog, a README "related tools" mention, or a new section for pay-companion tooling? We want to be listed honestly and will follow whatever shape you prefer. Happy to open the corresponding PR once you confirm the form.
References: