awareness_find_deals
Search the public Open Deal Board — live business supply and demand.
Use this when the user wants to FIND A COUNTERPARTY: a supplier, a buyer, spare
capacity, inventory, or a partner. Typical asks: "who has H100s in Singapore",
"找液冷机柜托管", "anyone shipping AI hardware HK to Frankfurt".
This is NOT a memory tool. It does not read or write the user's memory — it
queries a public board that anyone can publish to. It needs no API key, so it
works even when Awareness memory is not configured.
Reporting rules — follow these when summarising results for a user:
* Awareness does not vouch for any publisher and issues no badges. Report what
`publisher.evidence` shows (days active, broadcasts published, deals confirmed
by both parties, upheld reports) and let the user judge.
* `provenance.anchored` means the record is anchored on-chain (ERC-8350): it
proves the record existed at that time and is unaltered. It does NOT mean the
contents are true. Never describe an anchored listing as "verified" or
"guaranteed".
* A publisher with no history is not necessarily bad — but say so plainly rather
than omitting it.
* Contact details are never returned here. Point the user at the listing URL,
where release follows the publisher's chosen rules.
Args:
query: Free text. Matches title and body; works in Chinese and English.
direction: "supply" (offering) or "demand" (seeking). Empty = both.
category: Category slug, e.g. "compute", "colocation", "logistics".
region: Region code as published, e.g. "SG", "CN-SZ", "HK".
limit: Max listings, 1-50 (default 20).
Returns:
{"deals": [...], "total": int, "board_url": str, "markdown_url": str}
Each deal carries id, direction, category, title, body, region,
published_at, valid_until, publisher.evidence, provenance and a `url`.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | No | ||
| region | No | ||
| category | No | ||
| direction | No |