Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,7 @@ Bankr Skills equip builders with plug-and-play tools to build more powerful agen
| [Hydrex](https://hydrex.fi) | [hydrex](hydrex/) | Liquidity pools on Base. Lock HYDX for voting power, vote on pool strategies, deposit single-sided liquidity into auto-managed vaults, and claim oHYDX rewards. |
| [Helixa](https://helixa.xyz) | [helixa](helixa/) | Onchain identity and reputation for AI agents on Base. Mint identity NFTs, check Cred Scores, verify social accounts, update traits/narrative, and query the agent directory. Supports SIWA auth and x402 micropayments. |
| [Polygon](https://polygon.technology) | [trails](trails/) | Cross-chain swap, bridge, and DeFi orchestration via Sequence. Swap tokens across chains, bridge assets, fund a Bankr wallet from any chain, deposit into yield vaults (Aave, Morpho), get token prices, and discover earn pools. Integrates with Bankr submit() for on-chain execution. |
| [Temporal](https://temporal.rest) | [temporal-rest](temporal-rest/) | Paid research reports, archive answers, live signals, and durable workflows on Tempo. Discover capabilities, preview spend, run async jobs, and create recurring subscriptions via x402. |
| [0xWork](https://0xwork.org) | [0xwork](0xwork/) | Decentralized task marketplace on Base. AI agents discover, claim, and complete tasks paid in USDC with on-chain escrow. Supports services, products, and reputation. |
| [BOTCOIN](https://botcoin.money) | [BOTCOIN](BOTCOIN/) | Mine BOTCOIN by solving AI-powered hybrid challenges on Base. Stake-gated V2 mining with on-chain reward claims via Bankr. |

Expand Down
128 changes: 128 additions & 0 deletions temporal-rest/SKILL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,128 @@
---
name: temporal-rest
description: Temporal - paid research reports, archive answers, live signals, and durable workflow execution via temporal.rest. Use when an agent wants to discover Temporal capabilities, buy structured reports, query the published archive, preview workflow spend and touched capabilities, run async jobs, create recurring workflow subscriptions, or monitor live signals on Tempo. Triggers on temporal.rest, Temporal, paid report, archive answer, workflow preview, topic_brief, launch_tracker, partner_monitor, competitor_watch, signal_explain, or Tempo x402 workflow APIs.
metadata: {"clawdbot":{"homepage":"https://temporal.rest","requires":{"bins":["curl","jq"]}}}
---

# Temporal

Temporal is a paid research and workflow harness on Tempo.

Public surface:

- Free discovery at `https://temporal.rest/api`
- Free workflow preflight at `https://temporal.rest/api/workflows/preview`
- Paid reports at `/api/report/*`
- Paid data at `/api/data/*`
- Paid inline and async workflows at `/api/workflows/*`

## Quick Start

Start with free discovery before opening a paid route.

```bash
curl -s https://temporal.rest/api | jq '.endpoints[] | {path, pricing, category}'
```

Preview workflow cost, touched capabilities, approval risk, and likely artifacts before paying:

```bash
curl -G -s https://temporal.rest/api/workflows/preview \
--data-urlencode intent=job \
--data-urlencode template=topic_brief \
--data-urlencode topic='tempo mainnet' | jq
```

Paid routes require a Tempo or x402-capable client. If you already use the Tempo CLI, the same endpoints work there:

```bash
tempo request -X GET https://temporal.rest/api/data/latest
tempo request -X GET 'https://temporal.rest/api/data/answer?q=tempo%20mainnet'
tempo request -X GET 'https://temporal.rest/api/workflows/run?template=signal_explain&topic=Launch%20anchor%20Tempo%20mainnet'
```

## What To Use When

### Reports

- `GET /api/report/standard` - latest full nightly synthesis, `$1`
- `GET /api/report/alpha` - higher-conviction operator framing, `$3`
- `GET /api/report/executive` - compressed decision memo, `$5`

Use reports when the user wants the latest packaged research product rather than a workflow receipt.

### Data

- `GET /api/data/latest` - latest machine-readable snapshot, `$0.05/query`
- `GET /api/data/answer?q=...` - topic-specific archive answer, `$0.15/query`
- `GET /api/data/signals` - distilled signals, optional `slug` or `label`, `$0.05/query`

Use data routes when the user wants lightweight machine access without running a workflow.

### Workflows

- `GET /api/workflows/preview` - free preflight quote and policy view
- `GET /api/workflows/run` - inline paid workflow run, `$0.25/job`
- `POST /api/workflows/jobs` - persisted async job, `$0.25/job`
- `POST /api/workflows/subscriptions` - recurring subscription with optional webhook delivery, `$10/subscription`

Use:

- `run` for one-shot paid execution when the user wants the completed result immediately
- `jobs` when the user needs a durable receipt, polling, event history, or resume support
- `subscriptions` when the user wants the same workflow rerun on a cadence

## Workflow Templates

Common templates:

- `topic_brief` - short research brief for a topic
- `launch_tracker` - launch-focused brief for a topic
- `daily_operator_watch` - watchlist pass over a focus area
- `partner_monitor` - partner-specific monitoring by focus
- `competitor_watch` - competitor-oriented watch by focus
- `signal_explain` - explain a specific signal thread with archive context

Template input shape is small and typed:

```json
{
"template": "partner_monitor",
"focus": "payments",
"slug": "2026-03-21"
}
```

Rules:

- Brief-style templates usually use `topic`
- Watch-style templates usually use `focus`
- `slug` is optional and pins the workflow to a published issue

## Common Recipes

### Discover the live capability manifest

```bash
curl -s https://temporal.rest/api | jq
curl -s https://temporal.rest/api/capabilities | jq '.capabilities[] | {name, path: .endpoint.path, pricing: .pricingModel}'
```

### Run an async job and then poll it

1. Preview the job first.
2. Submit `POST /api/workflows/jobs` with a paid client.
3. Poll the returned `statusPath` or `eventsPath` until terminal state.
4. Read the final receipt, artifacts, and verification block.

### Create a recurring subscription

Use `POST /api/workflows/subscriptions` with:

- `template`
- `topic` or `focus`
- `intervalHours`
- optional `webhookUrl`
- optional `notifyMode=material_change` or `notifyMode=always`

See [references/public-api.md](references/public-api.md) for endpoint tables, template guidance, and the workflow lifecycle.
105 changes: 105 additions & 0 deletions temporal-rest/references/public-api.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,105 @@
# Temporal public API reference

Temporal exposes a public paid surface for research, data, and workflows.

## Discovery and docs

| Route | Access | Purpose |
| --- | --- | --- |
| `/api` | free | compact service summary with endpoint list, pricing, latest report, and discovery links |
| `/api/capabilities` | free | full machine-readable manifest with schemas, quotes, and reliability hints |
| `/capabilities` | free | human-readable capability docs |
| `/signals` | free | public live signal board |

## Paid routes

| Route | Method | Price | Use |
| --- | --- | --- | --- |
| `/api/report/standard` | `GET` | `$1` | full latest nightly synthesis |
| `/api/report/alpha` | `GET` | `$3` | operator framing and high-conviction packaging |
| `/api/report/executive` | `GET` | `$5` | compressed decision memo |
| `/api/data/latest` | `GET` | `$0.05/query` | latest machine-readable snapshot |
| `/api/data/answer` | `GET` | `$0.15/query` | archive-backed answer for `q` |
| `/api/data/signals` | `GET` | `$0.05/query` | distilled signals, optionally filtered by `slug` or `label` |
| `/api/workflows/run` | `GET` | `$0.25/job` | inline paid workflow run |
| `/api/workflows/jobs` | `POST` | `$0.25/job` | durable async workflow submission |
| `/api/workflows/subscriptions` | `POST` | `$10/subscription` | recurring workflow lane with optional webhook delivery |

`/api/workflows/preview` is free and should be called first whenever the user is deciding whether to run a workflow.

## Workflow input patterns

Current public templates:

- `topic_brief`
- `launch_tracker`
- `daily_operator_watch`
- `partner_monitor`
- `competitor_watch`
- `signal_explain`
- `deep_report_create`
- `deep_report_refresh`

Parameter rules:

- brief-oriented templates usually take `topic`
- watch-oriented templates usually take `focus`
- `slug` is optional and selects a specific published issue
- subscriptions also take `intervalHours`
- subscriptions can add `webhookUrl`
- subscriptions can set `notifyMode=material_change` or `notifyMode=always`

Useful preview example:

```bash
curl -G -s https://temporal.rest/api/workflows/preview \
--data-urlencode intent=job \
--data-urlencode template=partner_monitor \
--data-urlencode focus=payments | jq
```

## Workflow lifecycle

### Inline run

Use `GET /api/workflows/run` when the user wants a one-shot workflow result and does not need queueing.

Typical flow:

1. Call preview.
2. Open the paid route with a Tempo or x402-capable client.
3. Read the completed receipt, spend block, result, verification, and any artifact handles.

### Async job

Use `POST /api/workflows/jobs` when the user needs durable state or may need to resume later.

Typical flow:

1. Call preview.
2. Submit the job.
3. Poll `statusPath`.
4. Read `eventsPath` for node-level progress.
5. If the job fails and a `resumePath` is returned, resume that job instead of creating a duplicate.

### Subscription

Use `POST /api/workflows/subscriptions` when the user wants recurring execution.

Typical flow:

1. Preview a comparable one-off run.
2. Create the subscription.
3. Store the returned subscription id and status path.
4. Watch webhook deliveries or poll the subscription ledger for due runs.

## Trust model

Useful details from the manifest:

- capability manifests include signed discovery quotes and schema hashes
- workflow preview returns a deterministic preview hash
- paid responses include capability metadata and proof references
- commitments point at an identity ledger and signal scoreboard onchain

Treat discovery as guidance and the live x402 challenge as authoritative.