@vapi-network/mcp 0.1.0 → 0.2.0-dev.2

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -1,176 +1,211 @@
-# Agent Cash (`@vapi-network/mcp`)
+# vAPI Network
 
-Agent Cash gives Claude, Cursor, and other MCP clients a small local wallet that
-can discover and pay x402 APIs directly.
+**One wallet, every x402 API.** vAPI Network is an open-source, non-custodial
+TypeScript toolkit for discovering and paying x402 services from a CLI, MCP
+client, or your own code. Call works today. Tasks and Compute are next.
 
-For the Call launch, this buyer-local client is the npm-distributed payment path
-for native and external Bazaar listings. The browser-wallet flow is also
-available where a provider permits a direct browser request. Legacy wrapped
-rows remain hidden and non-callable while the optional Wrap gateway is disabled.
-The hosted Go MCP remains free (`echo` and `search`).
+Your key stays encrypted on your machine. vAPI Network applies spend policy
+before signing, sends payment directly to the service, and writes receipts to a
+local append-only ledger. It does not hold funds, proxy payments, or send
+telemetry off the machine by default.
 
-The private key is generated locally and stored only in the Agent Cash home
-(default `~/.vapi/agent-cash`, overridden by `VAPI_AGENT_CASH_HOME`), encrypted
-with scrypt (`N=2^15`) and AES-256-GCM. Your MCP client signs each exact
-EIP-3009 payment locally. vAPI supplies public discovery metadata; it never
-receives the private key and cannot spend the wallet balance. Fund this like
-pocket money, not a treasury.
+## 60-second quickstart
 
-Direct x402 calls need no vAPI account or API key: the agent pays the selected
-API directly from the buyer-controlled wallet.
+Install once, then every command is `vapi …`:
 
-## Install and run
+```bash
+npm i -g vapi-network
+vapi init                      # encrypted wallet + config under ~/.vapi (or $VAPI_HOME), prints the address
+```
 
-Create the encrypted local wallet:
+Fund that address with USDC on Base. Then:
 
-```sh
-npx -y @vapi-network/mcp init
+```bash
+vapi search "weather"          # every catalog, merged, with provenance
+vapi inspect <listing-ref>     # request contract and the live 402 quote, before paying
+vapi pay <listing-ref> --max 0.02
+vapi balance
+vapi receipts                  # one line per paid call: quote, settlement, latency
 ```
 
-Running `npx -y @vapi-network/mcp` with no command starts the MCP stdio server.
+No install? Prefix any command with `npx vapi-network`, for example `npx vapi-network init`.
+(`npx vapi` cannot work: the bare `vapi` name on npm belongs to an unrelated package.)
 
-Fund the printed address with a small amount of canonical Base-mainnet USDC
-(`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). Agent Cash does not need ETH to
-authorize ordinary x402 calls; send a little Base ETH only if you want it to
-sweep USDC back to another wallet later.
+### Use it from an agent (MCP)
 
-Configure an MCP client to launch the package through npm:
+Add this to Claude Desktop, Claude Code, or Cursor. The passphrase unlocks the local keystore; it never leaves the machine.
 
 ```json
 {
   "mcpServers": {
-    "agent-cash": {
+    "vapi": {
       "command": "npx",
-      "args": ["-y", "@vapi-network/mcp", "serve"],
-      "env": {
-        "VAPI_KEYSTORE_PASSWORD": "replace-with-your-keystore-passphrase"
-      }
+      "args": ["-y", "vapi-network", "mcp"],
+      "env": { "VAPI_KEYSTORE_PASSWORD": "your-passphrase" }
     }
   }
 }
 ```
 
-`VAPI_AGENT_CASH_HOME` optionally moves the wallet directory from
-`~/.vapi/agent-cash`. Desktop MCP hosts normally need
-`VAPI_KEYSTORE_PASSWORD` in the process environment because they cannot answer
-an interactive passphrase prompt. Protect that configuration with the same
-care as the pocket-money wallet.
-
-For a workspace-only development run, build from the repository root and keep
-the test wallet isolated under the gitignored `.context` directory:
-
-```sh
-pnpm --filter @vapi-network/mcp build
-VAPI_AGENT_CASH_HOME="$PWD/.context/agent-cash" \
-  pnpm --filter @vapi-network/mcp exec node dist/cli.js init
+Tools: `call.search`, `call.inspect`, `call.pay`, `wallet.address`, `wallet.balance`, `receipts.list`.
+Spend caps default to $0.10 per call and $1.00 per day; the wallet checks both before it signs.
+
+## Discovery sources
+
+Discovery is a plugin interface. The client can merge listings from multiple
+sources, de-duplicate them by resource URL, and retain each listing's
+provenance:
+
+- **vAPI Registry** is enabled by the default distribution, using
+  `https://api.vapinetwork.ai/api/call/discovery` for discovery and
+  `https://api.vapinetwork.ai/api/call/services` for service details. If the
+  primary returns HTTP 404 or cannot be resolved, the client logs one notice
+  and tries the configured fallback at `https://console.vapinetwork.ai`.
+- **Coinbase Bazaar** reads the public x402 v2
+  `/discovery/resources` catalog exposed by a facilitator.
+- **Local file** reads a JSON array of listings for private or development
+  catalogs.
+- **x402scan** is a deliberate stub for now. The source research documents its
+  discovery convention, but not a stable public read API that this client can
+  safely target.
+
+Use `@vapi-network/sources` to compose only the catalogs you trust. Network
+access is guarded against local and private destinations before a request is
+made.
+
+Set `VAPI_REGISTRY_URL` to replace the registry base; the client derives
+`/api/call/discovery` and `/api/call/services` beneath it. The existing
+`VAPI_MARKETPLACE_DISCOVERY_URL` and `VAPI_DISCOVERY_URL` variables can still
+override either full endpoint separately. Registry fallbacks are stored in
+`config.json` under `registryFallbacks`.
+
+## Packages
+
+| Package                 | Purpose                                                                  |
+| ----------------------- | ------------------------------------------------------------------------ |
+| `@vapi-network/core`    | x402 protocol, wallet, spend policy, discovery merge, and receipts       |
+| `@vapi-network/sources` | vAPI Registry, Coinbase Bazaar, local-file, and x402scan source adapters |
+| `@vapi-network/mcp`     | stdio MCP server with namespaced payment tools                           |
+| `@vapi-network/cli`     | `init`, discovery, payment, wallet, receipt, and MCP commands            |
+| `vapi-network`          | zero-dependency distribution with the `vapi` binary and defaults         |
+
+Every npm tarball is bundled and has zero runtime dependencies. The scoped
+packages are useful for embedding; most users should start with
+`vapi-network`.
+
+## SDK
+
+The core and source packages can be used without the CLI or MCP layer. See the
+runnable [SDK example](./examples/pay-with-sdk.ts) for discovery, policy
+validation, local signing, and direct x402 payment construction.
+
+Run it after initialization with `pnpm example:pay -- weather`.
+
+## Local state and migration
+
+By default, local state lives in `~/.vapi/`:
+
+```text
+config.json
+keystore.json
+receipts.jsonl
+spend-ledger.json
 ```
 
-For the first staging test, send a small amount of Base USDC to the printed
-address. Also send a little Base ETH only if you intend to test sweep-back.
-
-Then point the MCP client at the built CLI. Replace both absolute paths with
-this checkout's paths:
+Set `VAPI_HOME` to use a different directory. On first use of the default home,
+the client copies an existing `~/.vapi/agent-cash/` configuration into
+`~/.vapi/` when it can do so without overwriting files, prints a migration
+notice, and leaves the old directory untouched.
 
-```json
-{
-  "mcpServers": {
-    "agent-cash": {
-      "command": "node",
-      "args": ["/absolute/path/to/vapi-app/packages/vapi-mcp/dist/cli.js", "serve"],
-      "env": {
-        "VAPI_AGENT_CASH_HOME": "/absolute/path/to/vapi-app/.context/agent-cash",
-        "VAPI_KEYSTORE_PASSWORD": "replace-with-your-keystore-passphrase"
-      }
-    }
-  }
-}
-```
+## Metrics
 
-Base uses its public RPC by default. Leave `ARC_TESTNET_RPC_URL` unset for the
-Base-only staging slice.
+vAPI measures call and discovery health locally. Call receipts can include the
+listing name and provider host, policy decision, retry count, client version,
+outcome, total latency, and discovery, quote, signing, request, and settlement
+phase timings. Policy declines are recorded with the quoted amount but without
+a payer or transaction, so blocked spend remains visible without creating a
+payment authorization. Search events record the query, sources tried,
+per-source latency and result count, merged result count, and timestamp.
 
-Restart the MCP client. The agent can now:
+Call receipts are appended to `$VAPI_HOME/receipts.jsonl`; search events are
+appended to `$VAPI_HOME/searches.jsonl`. Nothing in either ledger is uploaded,
+and vAPI sends no telemetry off the machine by default. The vAPI website can
+show public on-chain usage for a wallet address directly from the chain; that
+view does not require uploading these local files.
 
-- `search {query?, kinds?, network?, limit?, cursor?}` across the public
-  marketplace. API results are callable; other results carry their canonical
-  vAPI web action.
-- `call {id|url, method?, body?, maxPriceUsd?, network?}` and pay an x402
-  `exact` challenge directly over HTTPS. An `id` must be an API ref returned by
-  `search` in the current Agent Cash process; an explicit published `url` may be
-  called directly. Set `network` to require a specific configured CAIP-2
-  network before Agent Cash signs.
-- `wallet {}` to inspect the address and USDC balance on each network.
+Use `vapi stats --range 24h|7d|30d` for a human-readable summary or add `--json`
+for the stable `{ range, generatedAt, totals, outcomes, latency, topServices,
+search }` shape. `receipts.stats` exposes the same shape through MCP. Export raw
+receipts for spreadsheets and dashboards with:
 
-`tools/list` exposes exactly these three tools: `search`, `call`, and `wallet`.
+```sh
+vapi receipts export --format json --range 30d
+vapi receipts export --format csv --range 30d
+```
 
-## Spend caps
+## Roadmap
 
-The Agent Cash home's `config.json` contains atomic-USDC caps (USDC has 6 decimals):
+- A local gateway daemon (`vapi serve`) with per-key budgets
+- OpenTelemetry traces and metrics, with exporters enabled only by the user
+- `task.*` tools for posting, funding, delivering, and reviewing work
+- `compute.*` tools for discovering models and paying for inference
 
-```json
-{
-  "spendCaps": {
-    "perCallAtomic": "100000",
-    "perDayAtomic": "1000000"
-  }
-}
-```
+Until the gateway lands, `vapi serve` and the provider-side `vapi publish`
+command exit with a preview message. Payments remain direct from the local
+wallet to each service.
 
-Those defaults are $0.10 per call and $1.00 per UTC day. Agent Cash checks both caps and reserves the quote in its atomic local daily ledger **before signing**. `maxPriceUsd` can set a still-lower ceiling for one tool call. The ledger is `spend-ledger.json` in the same Agent Cash home and rolls over when the UTC date changes.
+## Development
 
-The `call` tool requires HTTPS and blocks private, loopback, and link-local destinations by default. It validates every redirect before carrying a method or body forward. For local development only, setting `"allowPrivateNetwork": true` in `~/.vapi/agent-cash/config.json` permits an unpaid HTTP `localhost`, `*.localhost`, or loopback request; it does not permit HTTP calls to remote hosts, and Agent Cash still refuses to send a signed payment over HTTP.
+This is a pnpm workspace for Node.js 22 and pnpm 10.
 
-`discoveryUrl` remains the Calls compatibility endpoint used to resolve a
-searched native vAPI ref into its payable endpoint. `marketplaceDiscoveryUrl`
-is the unified search route. Override them independently with
-`VAPI_DISCOVERY_URL` and `VAPI_MARKETPLACE_DISCOVERY_URL`. Agent Cash rejects an
-uncached or evicted `id` because its source and marketplace kind are no longer
-known; run `search` again or use the result's explicit published URL. It never
-attempts to call a service offer or open request; those actions continue in the
-web marketplace.
+```sh
+pnpm install
+pnpm lint
+pnpm typecheck
+pnpm test
+pnpm build
+pnpm pack:check
+```
 
-## Paid-call receipts
+See [CONTRIBUTING.md](./CONTRIBUTING.md) for the development workflow and
+[SECURITY.md](./SECURITY.md) for private vulnerability reports.
 
-The `call` result keeps both payment receipt surfaces under `payment`:
+CLI commands exit `0` on success, `1` on an operational failure, and `2` for
+invalid usage or an announced preview-only command. `--json` sends both success
+values and errors to stdout as one JSON value; `mcp --json` is accepted as a
+no-op because the stdio transport is already JSON-RPC.
 
-- `settlement` is the decoded x402 `Payment-Response` (or compatible `X-Payment-Response`) header.
-- `proof` is normally `null` for launch-approved native endpoints. Agent Cash
-  preserves an `X-VAPI-Payment-Proof` value if a future reviewed Wrap endpoint
-  returns one.
+## Publishing
 
-A proof value alone is not verification. A future Wrap consumer must pin and
-verify its signer and fields and enforce replay protection.
+All five packages share one version and are published together. npm reads a
+package manifest before lifecycle hooks run, so the release is made from the
+generated `publish/` directories, never from the workspace package roots.
 
-## Balances and sweep-back
+First update every package to the same version, keep
+`publishConfig.tag = "next"`, and verify the exact tarballs:
 
 ```sh
-VAPI_AGENT_CASH_HOME="$PWD/.context/agent-cash" pnpm --filter @vapi-network/mcp exec node dist/cli.js balance
-VAPI_AGENT_CASH_HOME="$PWD/.context/agent-cash" pnpm --filter @vapi-network/mcp exec node dist/cli.js sweep-back 0xYourMainWallet
-VAPI_AGENT_CASH_HOME="$PWD/.context/agent-cash" pnpm --filter @vapi-network/mcp exec node dist/cli.js sweep-back 0xYourMainWallet --network eip155:8453
+pnpm install --frozen-lockfile
+pnpm pack:check
 ```
 
-Without `--network`, sweep-back attempts every configured network. Base transfers the full USDC balance because gas is paid in ETH. Arc gas is paid in USDC, so Agent Cash keeps 0.05 USDC by default instead of stranding the sweep transaction. Configure that reserve with `VAPI_ARC_GAS_HEADROOM_USDC` (for example, `0.10`).
-
-## Networks
+After reviewing the output, a maintainer with npm access runs these commands
+manually:
 
-| Network      | CAIP-2           | Chain ID | USDC                                         | Gas token | RPC                                                    |
-| ------------ | ---------------- | -------: | -------------------------------------------- | --------- | ------------------------------------------------------ |
-| Base mainnet | `eip155:8453`    |     8453 | `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` | ETH       | `BASE_RPC_URL`, defaults to `https://mainnet.base.org` |
-| Arc testnet  | `eip155:5042002` |  5042002 | `0x3600000000000000000000000000000000000000` | USDC      | `ARC_TESTNET_RPC_URL` is required                      |
-
-Agent Cash configures Base only by default. For the staging test, first run
-`search {"query":"<capability>","kinds":["api"],"network":"eip155:8453"}`.
-In the same Agent Cash process, call the returned ref with
-`call {"id":"<search-result-ref>","network":"eip155:8453","maxPriceUsd":"0.02"}`.
-Arc remains opt-in: set a nonblank `ARC_TESTNET_RPC_URL` to add it. The same
-exact-scheme EIP-3009 code path handles both CAIP-2 networks. You can also edit
-the `networks` map in `~/.vapi/agent-cash/config.json`; entries with blank RPC
-URLs are ignored and cannot be selected for payment. A custom token/network
-entry must pin its EIP-712 domain as `"eip712Domain": { "name": "…", "version":
-"…" }`; provider-supplied domain text is never trusted on its own.
+```sh
+npm login
+pnpm --dir packages/core publish:npm
+pnpm --dir packages/sources publish:npm
+pnpm --dir packages/mcp publish:npm
+pnpm --dir packages/cli publish:npm
+pnpm --dir packages/vapi-network publish:npm
+```
 
-## Custody and recovery
+Each package's `publish:npm` script publishes its staged `./publish` directory
+with `npm publish ./publish --access public --tag next`. The manual release
+workflow verifies and prints these commands; it never receives npm credentials
+or publishes automatically.
 
-This package is self-custodied software: the encrypted payment key and spend ledger live on your machine. vAPI is discovery only in this lane. Vendors receive only narrowly scoped EIP-3009 authorizations for the exact quoted amount, recipient, token, chain, nonce, and validity window. A stolen unlocked key or passphrase can still drain the wallet, so keep only a small working balance and sweep unused funds back.
+## License
 
-Back up the encrypted keystore if you need recovery. Losing both the keystore and its backup permanently loses access to its funds; losing the passphrase does too. Never share the decrypted private key.
+Apache-2.0. See [LICENSE](./LICENSE).

package/dist/index.d.ts

@@ -0,0 +1,4 @@
+export { callService, createVapiServer, loadServerConfig, startStdioServer, type CallToolInput, type CallToolResult, type VapiServerOptions, } from "./server.js";
+export { inspectService, type InspectToolInput, type InspectToolResult } from "./tools/inspect.js";
+export { resolveServiceEndpoint, searchMarketplace, type MarketplaceSearchInput, } from "./tools/search.js";
+export { getWallet, type WalletBalance } from "./tools/wallet.js";