Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.myproceeds.xyz/llms.txt

Use this file to discover all available pages before exploring further.

The Events page shows every lifecycle step Proceeds emits while handling a paid request. Use it to answer one question: where did this flow stop?

​
Event types

EventMeaning
RequestThe client hit a paywall.
PaymentA payment payload was received and validated.
FulfillmentProceeds proxied the request to the upstream Target URL and got a successful response.
ErrorSomething failed at any step.
A healthy paid request emits Request → Payment → Fulfillment.

​
Filters

All, Request, Payment, Fulfillment, Error.

​
How to read the stream

Start at the latest event and walk backwards:
  1. Did Request fire? If not, the URL never reached Proceeds — check DNS or the client’s URL.
  2. Did Payment fire? If not, the client didn’t retry with proof, or the proof was rejected.
  3. Did Fulfillment fire? If not, the upstream call failed — see Forward upstream auth and Custom headers and query parameters.
If you see an Error event at any step, open it to see the underlying reason.

Cross-check payment state

Compare event traces against the matching transaction record.