@farthershore/cli 0.9.2 → 0.10.0

package/README.md

@@ -163,8 +163,10 @@ repo-backed product with `farthershore build --apply`.
 
 Plan pricing lives on the plan (see `farthershore plan create` below) — the
 product itself no longer carries a `billingStrategy`. Omitting both meter flags
-gives the product a `requests` meter; variable-value meters (tokens, credits,
-spend) are settled from upstream `x-fs-cost-{key}` response headers.
+gives the product a `requests` meter. Plain request counting is
+platform-managed. Variable-value meters such as tokens, credits, or compute must
+be declared in the Product SDK as route `reports` and reported by the upstream
+with `@farthershore/metering`.
 
 A new product starts as a DRAFT with a generated `frontend/` project ready for
 customization. Going live mirrors the dashboard's "Finish setting up" checklist:
@@ -250,6 +252,29 @@ Read recent usage off the management API.
 farthershore usage summary weather-api --format json
 ```
 
+### `farthershore metering-token`
+
+Provision runtime metering tokens for upstream services. Core stores only token
+hashes; the raw token is returned once and should be deployed as
+`FARTHERSHORE_METERING_TOKEN`.
+
+```bash
+farthershore metering-token list weather-api --format json
+farthershore metering-token create weather-api --name "prod-api" --format json
+farthershore metering-token create weather-api --name "preview-api" --env preview --format json
+farthershore metering-token revoke weather-api <tokenId> --yes --format json
+```
+
+Pair the token with `@farthershore/metering` in the upstream:
+
+```ts
+import { withUsage } from "@farthershore/metering";
+
+return withUsage(request, Response.json(result), {
+  tokens_used: result.tokensUsed,
+});
+```
+
 ### `farthershore connect`
 
 GitHub OAuth and Stripe Connect flows are browser-only. These commands