Sql from english · saved and checkable

This result could not be confirmed unchanged yet.

Sent using Zambo

Saved:
What was asked: The request recorded for this receipt.

Zambo is the verifiable work layer for AI.

Observed result

{"sql":"SELECT id, email, created_at FROM users WHERE created_at >= date_trunc('month', CURRENT_DATE) ORDER BY created_at ASC;","explanation":"Selects the id, email, and creation timestamp for all users whose signup date falls within the current calendar month, sorted chronologically from oldest to newest.","indexes_needed":["CREATE INDEX idx_users_created_at ON users (created_at);"],"performance_notes":"Using date_trunc('month', CURRENT_DATE) is sargable and allows the database to utilize an index on created_at efficiently. Avoid wrapping the column in functions like EXTRACT or DATE() in the WHERE clause, as this prevents index usage and forces a full table scan.","common_mistakes":"1. Using WHERE created_at = CURRENT_DATE (only gets today, not the month). 2. Using WHERE EXTRACT(MONTH FROM created_at) = EXTRACT(MONTH FROM CURRENT_DATE) (non-sargable, ignores year, and slow). 3. Forgetting to include the year in the comparison if using manual date construction.","variations":["SELECT id, email, created_at FROM users WHERE created_at >= date_trunc('month', CURRENT_DATE) AND created_at < date_trunc('month', CURRENT_DATE) + INTERVAL '1 month' ORDER BY created_at ASC;","SELECT id, email, created_at FROM users WHERE created_at >= make_date(CURRENT_DATE - INTERVAL '1 month', 1, 1) AND created_at < make_date(CURRENT_DATE, 1, 1) ORDER BY created_at ASC;"],"dialect":"postgresql"} $0.99 Day Pass · 24h access · USDC on Base — activate with day_pass_activate.

This is the saved result preview, not proof that the answer was correct.

Check this receipt Run your own
Show technical provenance details

Provenance for every timeline entry

  • EXECUTED BY ZAMBOZambo ran the tool call itself.
  • OBSERVED VIA GATEWAYA Zambo gateway observed request and response bytes from the named external executor. Zambo did not run that external action.
  • LOGGED BY AGENTAn agent or local hook reported the action. Zambo attests that the record is unchanged since logging, not that the action happened as described.

Private agent reasoning, built-in client actions, and direct calls to unrelated MCP servers are not included unless an agent or gateway reports them.

What is an execution receipt?

An execution receipt is a public record of a reported AI agent tool call. Its byte commitment and provenance claim can be checked independently; neither alone authenticates the issuer. Read the canonical definition of an AI agent execution receipt.

What the receipt can and cannot prove

What is this?

Zambo's receipt store reports a tool call and records its result. The SHA-256 commitment covers the exact canonical bytes. The provenance label is bound to v0.4 receipt bytes when that check passes, but no pinned signature or trusted issuer key is checked. An anchor can timestamp a fingerprint; it does not authenticate the issuer.

Keep the work moving

This receipt records a completed tool call. When the free allowance is not enough, choose the access path that fits the job.

UNLOCK 24H DAY PASS ($0.99) →

See all plans on the pricing page →

RUN YOUR OWN FREE CALL →

Or re-run this exact call, using the same tool and arguments.

Share this receipt

Share on X · Share on LinkedIn ·

Show technical verification checks

Verification checks

  • SHA-256 commitment: Checked independently against the exact decoded bytes
  • Provenance binding: LEGACY; legacy receipt, provenance not cryptographically bound
  • Metadata binding: LEGACY; legacy receipt, metadata is not cryptographically bound
  • Issuer authentication: NOT CHECKED; no pinned signing key or trusted issuer was supplied
  • Signature: NOT CHECKED; no Ed25519 signature or pinned key is supplied
  • Chain: NOT CHECKED; no append-only chain proof is validated
  • Stored timestamp: 2026-10-06T03:05:03.268Z; external immutability is not checked

Get proof like this from your own AI

Add to my AI ·

Get receipts for your own AI work: add zambo.dev/mcp

One URL, no key. Copy the line for your AI and add it yourself in its settings.

  • ClaudeSettings, Connectors, Add custom connector, paste the URL.
    https://zambo.dev/mcp
  • ChatGPTSettings, Apps and Connectors, developer mode, create a connector with this URL.
    https://zambo.dev/mcp
  • GrokAdd a remote MCP server in your Grok client and paste the URL.
    https://zambo.dev/mcp
  • CursorPaste into ~/.cursor/mcp.json.
    {"mcpServers":{"zambo":{"url":"https://zambo.dev/mcp"}}}

Nothing is installed automatically. Full setup guides

Want a verifiable receipt for every job your bots do?

Add Zambo Receipt Bot to your team · File this in Receipt Bot

Show receipt data and verification evidence

Committed provenance claim

EXECUTED BY ZAMBO

legacy receipt, provenance not cryptographically bound

Receipt ID
5d2092c7-f427-435d-9229-a14da6e836d5
SHA-256 output hash
sha256:31e056ad77dbd92bdb5600b143c06146b55fc4369e9415732447c6f5f7d47d76
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NDYyZTU4YTdjNzFlMjkwODM4MjUxM2EyYjNhYTY1MjZhZDg4MmUzMTVkYTU3NDY3MjhjOTQzMTMwYWVhNmRhNCIsInR5cGUiOiJhbm9ueW1vdXMifSwib3V0cHV0Ijp7InRleHQiOiJ7XCJzcWxcIjpcIlNFTEVDVCBpZCwgZW1haWwsIGNyZWF0ZWRfYXQgRlJPTSB1c2VycyBXSEVSRSBjcmVhdGVkX2F0ID49IGRhdGVfdHJ1bmMoJ21vbnRoJywgQ1VSUkVOVF9EQVRFKSBPUkRFUiBCWSBjcmVhdGVkX2F0IEFTQztcIixcImV4cGxhbmF0aW9uXCI6XCJTZWxlY3RzIHRoZSBpZCwgZW1haWwsIGFuZCBjcmVhdGlvbiB0aW1lc3RhbXAgZm9yIGFsbCB1c2VycyB3aG9zZSBzaWdudXAgZGF0ZSBmYWxscyB3aXRoaW4gdGhlIGN1cnJlbnQgY2FsZW5kYXIgbW9udGgsIHNvcnRlZCBjaHJvbm9sb2dpY2FsbHkgZnJvbSBvbGRlc3QgdG8gbmV3ZXN0LlwiLFwiaW5kZXhlc19uZWVkZWRcIjpbXCJDUkVBVEUgSU5ERVggaWR4X3VzZXJzX2NyZWF0ZWRfYXQgT04gdXNlcnMgKGNyZWF0ZWRfYXQpO1wiXSxcInBlcmZvcm1hbmNlX25vdGVzXCI6XCJVc2luZyBkYXRlX3RydW5jKCdtb250aCcsIENVUlJFTlRfREFURSkgaXMgc2FyZ2FibGUgYW5kIGFsbG93cyB0aGUgZGF0YWJhc2UgdG8gdXRpbGl6ZSBhbiBpbmRleCBvbiBjcmVhdGVkX2F0IGVmZmljaWVudGx5LiBBdm9pZCB3cmFwcGluZyB0aGUgY29sdW1uIGluIGZ1bmN0aW9ucyBsaWtlIEVYVFJBQ1Qgb3IgREFURSgpIGluIHRoZSBXSEVSRSBjbGF1c2UsIGFzIHRoaXMgcHJldmVudHMgaW5kZXggdXNhZ2UgYW5kIGZvcmNlcyBhIGZ1bGwgdGFibGUgc2Nhbi5cIixcImNvbW1vbl9taXN0YWtlc1wiOlwiMS4gVXNpbmcgV0hFUkUgY3JlYXRlZF9hdCA9IENVUlJFTlRfREFURSAob25seSBnZXRzIHRvZGF5LCBub3QgdGhlIG1vbnRoKS4gMi4gVXNpbmcgV0hFUkUgRVhUUkFDVChNT05USCBGUk9NIGNyZWF0ZWRfYXQpID0gRVhUUkFDVChNT05USCBGUk9NIENVUlJFTlRfREFURSkgKG5vbi1zYXJnYWJsZSwgaWdub3JlcyB5ZWFyLCBhbmQgc2xvdykuIDMuIEZvcmdldHRpbmcgdG8gaW5jbHVkZSB0aGUgeWVhciBpbiB0aGUgY29tcGFyaXNvbiBpZiB1c2luZyBtYW51YWwgZGF0ZSBjb25zdHJ1Y3Rpb24uXCIsXCJ2YXJpYXRpb25zXCI6W1wiU0VMRUNUIGlkLCBlbWFpbCwgY3JlYXRlZF9hdCBGUk9NIHVzZXJzIFdIRVJFIGNyZWF0ZWRfYXQgPj0gZGF0ZV90cnVuYygnbW9udGgnLCBDVVJSRU5UX0RBVEUpIEFORCBjcmVhdGVkX2F0IDwgZGF0ZV90cnVuYygnbW9udGgnLCBDVVJSRU5UX0RBVEUpICsgSU5URVJWQUwgJzEgbW9udGgnIE9SREVSIEJZIGNyZWF0ZWRfYXQgQVNDO1wiLFwiU0VMRUNUIGlkLCBlbWFpbCwgY3JlYXRlZF9hdCBGUk9NIHVzZXJzIFdIRVJFIGNyZWF0ZWRfYXQgPj0gbWFrZV9kYXRlKENVUlJFTlRfREFURSAtIElOVEVSVkFMICcxIG1vbnRoJywgMSwgMSkgQU5EIGNyZWF0ZWRfYXQgPCBtYWtlX2RhdGUoQ1VSUkVOVF9EQVRFLCAxLCAxKSBPUkRFUiBCWSBjcmVhdGVkX2F0IEFTQztcIl0sXCJkaWFsZWN0XCI6XCJwb3N0Z3Jlc3FsXCJ9XG5cbiQwLjk5IERheSBQYXNzIMK3IDI0aCBhY2Nlc3MgwrcgVVNEQyBvbiBCYXNlIOKAlCBhY3RpdmF0ZSB3aXRoIGRheV9wYXNzX2FjdGl2YXRlLiJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC4zIiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJzcWxfZnJvbV9lbmdsaXNoIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
Timestamp

Bound call context

Receipt schema
0.3
Tool name
sql_from_english
Tool version
4.0.0
Permission scope
public
Caller type
anonymous
Caller ID
sha256:462e58a7c71e2908382513a2b3aa6526ad882e315da5746728c943130aea6da4
Declared side effects
none
Side-effects schema
zambo-side-effects/1
Declaration hash
sha256:45aad38f3aa982b9aafe92ecb416ebe98791eddbaf8ab6df0bd08605b7c1bfee

This records what the server-side tool contract declared at call time. It does not independently verify that a downstream side effect happened.

Bound upstream evidence

Status
no_upstream_bytes_captured
Evidence SHA-256
unavailable
Byte length
unavailable

Neutral Nostr anchor

Event ID
afc3f1a4e6d6a2cb73a572f46e67d7f62b188f049d9920ab8bf7ab6fd37ae058
Anchor status
partial
Public key
e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

Relay hints: wss://relay.damus.io · wss://nos.lol · wss://relay.primal.net

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-10-06T03:05:03.166Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:31e056ad77dbd92bdb5600b143c06146b55fc4369e9415732447c6f5f7d47d76","receipt_uuid":"5d2092c7-f427-435d-9229-a14da6e836d5","schema_version":"zambo-receipt-anchor/1"}

Anchor status "partial": Published to some configured relay targets; publication was not confirmed by every configured relay.

Check this hash yourself

Receipt commitment: verification_failed. This checks the saved bytes, not whether the answer was correct. Recompute the SHA-256 commitment in your browser. Open the API v2 JSON response to inspect the machine-readable checks. See the Nostr anchor event on a public viewer. The fingerprint is timestamped outside Zambo too.

Embed this receipt

Markdown

[![Verifiable Zambo receipt](https://zambo.dev/api/receipt/5d2092c7-f427-435d-9229-a14da6e836d5/badge.svg)](https://zambo.dev/run/5d2092c7-f427-435d-9229-a14da6e836d5?ref=badge)

HTML

<a href="https://zambo.dev/run/5d2092c7-f427-435d-9229-a14da6e836d5?ref=badge"><img src="https://zambo.dev/api/receipt/5d2092c7-f427-435d-9229-a14da6e836d5/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

62,148 verifiable receipts minted

RUN YOUR OWN FREE CALL →

Get your own: connect https://zambo.dev/mcp. Free daily calls, no API key.

Open the interactive receipt view

Your AI's work could look like this

Run a first job free in Zambo Chat. No account needed.

Start a free job Day Pass · $0.99 for 24 hours