@tempoxyz/mercator 0.0.1115 → 0.0.1174
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.
|
@@ -36,6 +36,12 @@ outcome. Follow the live tool schemas, descriptions, and returned next steps for
|
|
|
36
36
|
execution, and recovery. These server-provided instructions are updated independently of this skill.
|
|
37
37
|
If tools are unavailable, use `mercator-setup` or the host's native MCP connection controls.
|
|
38
38
|
|
|
39
|
+
- Pass file inputs, such as audio to transcribe, as public URLs; never inline file contents in a plan.
|
|
40
|
+
- Ask providers for URL outputs rather than inline base64 when they offer both.
|
|
41
|
+
- Keep list inputs to about 10 items per call and split larger batches.
|
|
42
|
+
- Prefer priced, healthy endpoints. After two failures of the same kind on one provider, stop
|
|
43
|
+
paying it and switch provider or report the failure.
|
|
44
|
+
|
|
39
45
|
## Feedback
|
|
40
46
|
|
|
41
47
|
- When an unexpected failure persists after one safe recovery attempt, proactively draft a report
|
|
@@ -11,14 +11,11 @@ paid job or a local payment wallet.
|
|
|
11
11
|
|
|
12
12
|
## Connect or repair
|
|
13
13
|
|
|
14
|
-
- **Diet Mercator (`https://mercator.sh/diet/mcp`)
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
the official Link CLI Balance-policy setup link. Ordinary card-checkout support alone does
|
|
20
|
-
not establish SPT support. Complete the Balance-policy steps below before calling automatic
|
|
21
|
-
payments ready.
|
|
14
|
+
- **Diet Mercator (`https://mercator.sh/diet/mcp`) is retired.** Replace that connection with
|
|
15
|
+
Mercator via Link at `https://mercator.link/mcp`, following `https://mercator.link/skill.md`.
|
|
16
|
+
Do not use the main wallet installer or request Tempo keys for it. Ordinary card-checkout support
|
|
17
|
+
alone does not establish SPT support; complete the Balance-policy steps below before calling
|
|
18
|
+
automatic payments ready.
|
|
22
19
|
- Identify the user's app and mode first; ask if unclear. Do not infer local terminal access
|
|
23
20
|
from the agent's ability to run commands in a sandbox.
|
|
24
21
|
- **Claude Desktop chat or claude.ai:** direct the user to **Customize → Connectors → Add custom
|
|
@@ -54,11 +51,11 @@ curl -fsSL https://mercator.sh/install.sh | sh
|
|
|
54
51
|
|
|
55
52
|
## Verify and recover
|
|
56
53
|
|
|
57
|
-
- For
|
|
54
|
+
- For Link-paid connections, check the compatible Link client's authentication, Balance availability and spending
|
|
58
55
|
authority separately. Use the official Link CLI setup/payment skills when the host can run it;
|
|
59
56
|
inspect command schemas and reuse existing authorization rather than creating duplicate grants.
|
|
60
57
|
Keep payment credentials inside that host. A native Link connection may expose only card checkout.
|
|
61
|
-
- Include policy setup in
|
|
58
|
+
- Include policy setup in Link onboarding when the user wants automatic Balance payments. Ask for
|
|
62
59
|
a finite per-purchase limit, explain that it is not a total task budget, and present the correct
|
|
63
60
|
app's official Link policy page for user review and approval. Reuse a verified existing policy;
|
|
64
61
|
never assume one exists from successful login. An approval-policy read `403` is inconclusive on
|