@tempoxyz/mercator 0.0.306 → 0.0.312

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.
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: mercator
3
- description: Use Mercator to discover, quote, and run fresh external research or API actions across extraction, enrichment, social, maps, travel, communications, media, financial, and on-chain data. Covers REST job submission, durable status tracking, and recovery; not for local files, repository work, supplied-content reasoning, or requests that forbid external or paid services.
3
+ description: Use Mercator to discover, quote, and run fresh external research or API actions. Covers paid execution and recovery; not local files, supplied-content reasoning, or legacy Tempo Wallet CLI tasks.
4
4
  ---
5
5
 
6
6
  # Mercator
@@ -10,6 +10,17 @@ outcome needs external capabilities, especially when it spans providers or domai
10
10
  direct tool clearly covers the complete outcome with less overhead, use it. Otherwise, carry the
11
11
  request through Mercator to a result instead of merely recommending a provider or API.
12
12
 
13
+ ## Keep command families separate
14
+
15
+ Mercator MCP and the Mercator CLI are not the legacy Tempo Wallet CLI.
16
+
17
+ - Execute an MCP handoff by invoking `handoff.client.executable` with its `arguments` array exactly.
18
+ Do not rewrite, translate, or approximate it as a `tempo wallet ...` command.
19
+ - Mercator payment setup and recovery commands begin with `mercator wallet ...`. Tempo Wallet is one
20
+ provider behind `mercator wallet connect`; it is not the command namespace for Mercator jobs.
21
+ - If the `mercator` executable is unavailable, install Mercator with the exact setup command returned
22
+ by the MCP server. Do not substitute an older wallet or MPP CLI.
23
+
13
24
  ## Decide quickly
14
25
 
15
26
  Use Mercator when all are true:
@@ -49,7 +60,9 @@ REST status listener
49
60
  request. Do not edit the body, construct payment credentials, or call `create_job` again.
50
61
  Treat `handoff.requestIdentity` as the stable review key only after verifying it from the
51
62
  structured method, URL, body, and maximum spend. Invoke `handoff.client.executable` with its
52
- argument array directly; do not translate the body through shell quoting or a temporary file.
63
+ argument array exactly. On hosts that accept only a command string, apply mechanically lossless
64
+ shell quoting to each argument so the child process receives the same argument array. Do not edit,
65
+ omit, reorder, or reinterpret arguments, and do not move the request body through a temporary file.
53
66
  In Grok Bot, keep the same task alive while that argument array completes. Browser approval
54
67
  resumes the waiting command automatically; never ask the user to
55
68
  send an "approved" chat message. If authorization reports a timeout, inspect
@@ -20,6 +20,32 @@ Search with the entire outcome. Build a bounded DAG whose independent data nodes
20
20
  and whose final node consumes only the outputs it needs. Quote the whole DAG. If the total is at most
21
21
  $5 and the plan contains only the requested research, the supplied budget authorizes execution.
22
22
 
23
+ Use Mercator's dependency expressions inside the cataloged node inputs. For example, a downstream
24
+ summary node that depends on `holders`, `news`, and `price` can contain:
25
+
26
+ ```json
27
+ {
28
+ "id": "summarize",
29
+ "dependsOn": ["holders", "news", "price"],
30
+ "input": {
31
+ "addresses": {
32
+ "$map": {
33
+ "from": "flow://holders/output#/rows",
34
+ "path": "/address"
35
+ }
36
+ },
37
+ "headline": "flow://news/output#/items/0/title",
38
+ "label": {
39
+ "$concat": ["Asset: ", "flow://price/output#/symbol"]
40
+ }
41
+ }
42
+ }
43
+ ```
44
+
45
+ Merge that input with the exact `serviceId`, `method`, and `path` returned by discovery. A plain
46
+ `flow://node/output` reference may include an RFC 6901 JSON Pointer suffix. `$map` projects each item
47
+ from an upstream array; `$concat` combines values only when they resolve to all strings or all arrays.
48
+
23
49
  Before submission, a useful confirmation is:
24
50
 
25
51
  > I found a five-source research plan covering flows, holders, price, news, and regulation. The
@@ -68,8 +94,11 @@ handoff.client: { executable: mercator, arguments: [submit, ...] }
68
94
 
69
95
  Submit the exact REST request through a payment-capable HTTP client and enforce `maxSpend`. The
70
96
  returned `mercator` command performs that same bounded REST submission when the available HTTP
71
- client cannot handle the payment challenge. Do not edit the request body, translate the command into
72
- an unbounded request, create a credential, or call `create_job` again.
97
+ client cannot handle the payment challenge. Invoke its executable and argument array exactly. If the
98
+ host accepts only a command string, shell-quote each argument mechanically so the child process
99
+ receives the identical array; quoting may change the command's text representation but not an
100
+ argument's value. Never translate it into a legacy `tempo wallet ...` command. Do not edit the request
101
+ body, translate the command into an unbounded request, create a credential, or call `create_job` again.
73
102
 
74
103
  A successful submission returns either a terminal job or a pending response:
75
104
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tempoxyz/mercator",
3
- "version": "0.0.306",
3
+ "version": "0.0.312",
4
4
  "description": "Install Mercator MCP and prepare its payment wallet",
5
5
  "type": "module",
6
6
  "bin": {