@catena/sdk 0.0.0-alpha-20260724191736
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +191 -0
- package/README.md +147 -0
- package/dist/client-DZHdFs_y.d.mts +566 -0
- package/dist/client-G-8NfBx_.mjs +597 -0
- package/dist/client.d.mts +2 -0
- package/dist/client.mjs +2 -0
- package/dist/keypair.d.mts +29 -0
- package/dist/keypair.mjs +43 -0
- package/dist/x402.d.mts +175 -0
- package/dist/x402.mjs +225 -0
- package/package.json +46 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,191 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
Copyright (c) 2025-2026 Catena Labs, Inc.
|
|
180
|
+
|
|
181
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
182
|
+
you may not use this file except in compliance with the License.
|
|
183
|
+
You may obtain a copy of the License at
|
|
184
|
+
|
|
185
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
186
|
+
|
|
187
|
+
Unless required by applicable law or agreed to in writing, software
|
|
188
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
189
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
190
|
+
See the License for the specific language governing permissions and
|
|
191
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,147 @@
|
|
|
1
|
+
# @catena/sdk
|
|
2
|
+
|
|
3
|
+
Typed client for the Catena agent API: read accounts, balances, and policy, move
|
|
4
|
+
money through policy-checked intents, and pay x402 (HTTP 402) challenges.
|
|
5
|
+
Node >= 20; no framework dependencies.
|
|
6
|
+
|
|
7
|
+
## Status: prerelease snapshots
|
|
8
|
+
|
|
9
|
+
Versions published under the `alpha` dist-tag are throwaway development
|
|
10
|
+
snapshots cut directly from the Catena monorepo. They carry no stability or
|
|
11
|
+
semver guarantees: any API may change or disappear between snapshots, and
|
|
12
|
+
snapshot versions (`0.0.0-alpha-<timestamp>`) never match ordinary semver ranges
|
|
13
|
+
— only an exact version, an explicit prerelease range, or a dist-tag like
|
|
14
|
+
`alpha` selects one.
|
|
15
|
+
|
|
16
|
+
```sh
|
|
17
|
+
npm install @catena/sdk@alpha
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
Pin the exact version you tested against; do not depend on the `alpha` tag
|
|
21
|
+
resolving to anything compatible over time.
|
|
22
|
+
|
|
23
|
+
## Entry points
|
|
24
|
+
|
|
25
|
+
- `@catena/sdk` — the client: `createCatenaClient`, intents, accounts,
|
|
26
|
+
counterparties, error types.
|
|
27
|
+
- `@catena/sdk/keypair` — generate or derive the P-256 credential and compute
|
|
28
|
+
its thumbprint.
|
|
29
|
+
- `@catena/sdk/x402` — a `fetch` wrapper that pays x402 402 challenges through
|
|
30
|
+
Catena.
|
|
31
|
+
|
|
32
|
+
## Authentication
|
|
33
|
+
|
|
34
|
+
Every request is signed (RFC 9421) with a P-256 private key; there are no API
|
|
35
|
+
tokens or sessions. The key must first be linked to a Catena agent by a host app
|
|
36
|
+
— for example the Catena CLI or the Catena console. How the key was generated
|
|
37
|
+
does not matter to this SDK, only that it is a valid P-256 key whose public half
|
|
38
|
+
is linked. The SDK derives the public half from `privateKeyHex` at construction
|
|
39
|
+
and never reads or writes stored credentials.
|
|
40
|
+
|
|
41
|
+
```ts
|
|
42
|
+
import { generateP256Keypair } from "@catena/sdk/keypair"
|
|
43
|
+
|
|
44
|
+
const keypair = generateP256Keypair()
|
|
45
|
+
// Persist keypair.privateKeyHex yourself; link keypair.publicKeyHex to an
|
|
46
|
+
// agent in a host app before the client can authenticate.
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
## Quickstart
|
|
50
|
+
|
|
51
|
+
```ts
|
|
52
|
+
import { createCatenaClient } from "@catena/sdk"
|
|
53
|
+
|
|
54
|
+
const client = createCatenaClient({
|
|
55
|
+
privateKeyHex: process.env.CATENA_PRIVATE_KEY!,
|
|
56
|
+
})
|
|
57
|
+
|
|
58
|
+
const { accounts } = await client.listAccounts()
|
|
59
|
+
const { counterparties } = await client.listCounterparties()
|
|
60
|
+
|
|
61
|
+
// The rail must match the method: "ach" and "wire" need a bank rail,
|
|
62
|
+
// "on-chain" needs a wallet rail. Pass the rail id, not the counterparty id.
|
|
63
|
+
const bankRail = counterparties
|
|
64
|
+
.flatMap((counterparty) => counterparty.rails)
|
|
65
|
+
.find((rail) => rail.type === "bank")!
|
|
66
|
+
|
|
67
|
+
const intent = await client.submitIntent({
|
|
68
|
+
action: {
|
|
69
|
+
type: "send",
|
|
70
|
+
accountId: accounts[0].id,
|
|
71
|
+
counterpartyRailId: bankRail.id,
|
|
72
|
+
// Decimal USD string: "12.50" is $12.50. Never cents or atomic units.
|
|
73
|
+
amount: "12.50",
|
|
74
|
+
method: "ach",
|
|
75
|
+
},
|
|
76
|
+
})
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
`submitIntent` returns a disposition, not a guarantee of execution — branch on
|
|
80
|
+
`intent.status`:
|
|
81
|
+
|
|
82
|
+
- `"completed"` — the action succeeded: money moved for send, transfer, and
|
|
83
|
+
wallet_send; for x402 the payment authorization was delivered (on-chain
|
|
84
|
+
settlement is verified separately); the counterparty exists for
|
|
85
|
+
create_counterparty.
|
|
86
|
+
- `"pending"` — parked, typically awaiting a human approval; `reasons` says why,
|
|
87
|
+
`expiresAt` says when the approval request lapses.
|
|
88
|
+
- `"processing"` — accepted and in progress. Executing intents advance on their
|
|
89
|
+
own; poll `getIntent(intent.id)`. An approved x402 payment instead rests here
|
|
90
|
+
until the paid request is re-run — polling never advances it.
|
|
91
|
+
- `"blocked"` — declined by policy or denied by an operator; `reasons` explains
|
|
92
|
+
why approval was required, not necessarily why it was denied. Terminal.
|
|
93
|
+
- `"failed"` — failed, expired, or reversed. Terminal.
|
|
94
|
+
|
|
95
|
+
## Errors
|
|
96
|
+
|
|
97
|
+
- `ApiError` — any non-OK API response. Branch on `code` (the stable error
|
|
98
|
+
code), not on message prose; `status` is the HTTP status.
|
|
99
|
+
- `IntentSubmitError` — `submitIntent` failed after the intent was created.
|
|
100
|
+
Branch on `outcome`: `"not-submitted"` means no money moved — recovery is a
|
|
101
|
+
new `submitIntent` with a fresh explicit `idempotencyKey` (omitting it replays
|
|
102
|
+
the same stranded intent); `"unknown"` means the server may have acted — poll
|
|
103
|
+
`getIntent(err.intentId)` to a terminal status and resubmit only after blocked
|
|
104
|
+
or failed, never blindly.
|
|
105
|
+
|
|
106
|
+
## Paying x402 challenges
|
|
107
|
+
|
|
108
|
+
`wrapFetchWithX402Payment` returns a drop-in `fetch`: when a response is a 402
|
|
109
|
+
with a decodable v2 challenge, it pays through Catena (policy checks included)
|
|
110
|
+
and retries once with the `PAYMENT-SIGNATURE` header. Everything else passes
|
|
111
|
+
through untouched.
|
|
112
|
+
|
|
113
|
+
```ts
|
|
114
|
+
import { createCatenaClient } from "@catena/sdk"
|
|
115
|
+
import { wrapFetchWithX402Payment } from "@catena/sdk/x402"
|
|
116
|
+
|
|
117
|
+
const client = createCatenaClient({
|
|
118
|
+
privateKeyHex: process.env.CATENA_PRIVATE_KEY!,
|
|
119
|
+
})
|
|
120
|
+
|
|
121
|
+
const fetchWithPayment = wrapFetchWithX402Payment(client, {
|
|
122
|
+
// Wallet account the payments draw from.
|
|
123
|
+
accountId: walletAccountId,
|
|
124
|
+
// Refuse challenges above this price, in atomic USDC units ("1000000" = $1).
|
|
125
|
+
maxAtomicAmount: 1_000_000n,
|
|
126
|
+
})
|
|
127
|
+
|
|
128
|
+
const response = await fetchWithPayment("https://api.example.com/paid-thing")
|
|
129
|
+
```
|
|
130
|
+
|
|
131
|
+
Request bodies must be replayable: pass them via the `init` argument as a
|
|
132
|
+
string, `URLSearchParams`, Blob, ArrayBuffer, or typed array — a `Request`
|
|
133
|
+
object carrying a body (or any stream) throws `X402PaymentError` instead of
|
|
134
|
+
paying.
|
|
135
|
+
|
|
136
|
+
Payment failures surface as `X402PaymentError` or a subclass documenting its
|
|
137
|
+
recovery path; an `ApiError` the loop does not absorb while skipping unpayable
|
|
138
|
+
candidates and a `"not-submitted"` `IntentSubmitError` propagate unchanged. Two
|
|
139
|
+
subclasses deserve care: `X402ApprovalPendingError` means the payment is parked
|
|
140
|
+
for human approval — re-run the same request after approval;
|
|
141
|
+
`X402RetryFailedError` and `X402SubmitInterruptedError` mean money may have
|
|
142
|
+
already moved — follow the recovery steps in the error message instead of paying
|
|
143
|
+
again.
|
|
144
|
+
|
|
145
|
+
## License
|
|
146
|
+
|
|
147
|
+
[Apache-2.0](./LICENSE)
|