com.publicdomainrelay.temp.market.bids.x402
Schema Diff
+1 -1
Compatibility Analysis
Backward Compatible
No changes detected.
1
1
{
2
2
"$type": "com.atproto.lexicon.schema",
3
3
"defs": {
4
4
"main": {
5
5
"description": "Includes pricing/payment terms and x402 endpoint for issuing a receipt against an accept.",
6
6
"key": "tid",
7
7
"record": {
8
8
"properties": {
9
9
"cost": {
10
10
"description": "Numeric price (integer or float) per the chosen frequency.",
11
11
"type": "unknown"
12
12
},
13
13
"currency": {
14
14
"description": "Currency code, e.g. 'USDC'.",
15
15
"type": "string"
16
16
},
17
17
"frequency": {
18
18
"description": "Billing frequency, e.g. 'monthly', 'hourly', 'one-time'.",
19
19
"type": "string"
20
20
},
21
21
"prepay": {
22
22
"description": "Whether payment is required before compute starts.",
23
23
"type": "boolean"
24
24
},
25
25
"url": {
26
-
"description": "Service DID reference (did:web:HOST#pdr_market) of the bidder's market service. The requester calls com.publicdomainrelay.temp.market.submitAccept via PDS service-proxying using this value as the atproto-proxy target, to settle the contract and obtain a receipt.",
26
+
"description": "x402 payment endpoint URL. To settle payment the requester first mints a com.publicdomainrelay.temp.market.accepts.x402 record, then issues an x402-gated GET to `{url}/{accepts.x402 AT-URI}/{accepts.x402 CID}`; on payment the bidder mints and returns a com.publicdomainrelay.temp.market.receipts.x402 proof-of-payment record. That receipt is then used as the payload of the higher-level com.publicdomainrelay.temp.market.accept.",
27
27
"type": "string"
28
28
}
29
29
},
30
30
"required": [
31
31
"cost",
32
32
"currency",
33
33
"frequency",
34
34
"prepay",
35
35
"url"
36
36
],
37
37
"type": "object"
38
38
},
39
39
"type": "record"
40
40
}
41
41
},
42
42
"id": "com.publicdomainrelay.temp.market.bids.x402",
43
43
"lexicon": 1
44
44
}