{
  "markdown": "# ArtifactGuard: Signed AI Deliverable QA\n\nUse ArtifactGuard as the last step before an AI agent delivers a JSON, ZIP,\nPDF, or DOCX file to a customer. The buyer receives a deterministic\n`PASS`, `WARN`, or `FAIL` receipt containing the artifact hash, contract hash,\nindividual checks, validator version, timestamp, and an Ed25519 signature.\n\n## One purchase case\n\nAn AI report agent creates `result.json`. Before delivery, it asks\nArtifactGuard to verify that the file is valid JSON, contains a `status` field\nequal to `ready`, and does not contain configured forbidden patterns. The agent\nthen attaches the signed receipt to its final handoff.\n\nThis is delivery-contract QA, not antivirus scanning, legal certification, or\na guarantee that the document's claims are true.\n\n## Buy through Apify\n\nSet your own Apify API token locally. Never commit it.\n\n```bash\nexport APIFY_TOKEN=\"your-token\"\ncurl --fail-with-body \\\n  -X POST \\\n  \"https://api.apify.com/v2/acts/analytical_gratefulness~artifactguard-agent/run-sync-get-dataset-items?format=json\" \\\n  -H \"Authorization: Bearer ${APIFY_TOKEN}\" \\\n  -H \"Content-Type: application/json\" \\\n  --data-binary @examples/validate_artifact.json \\\n  --output receipt-response.json\n```\n\n`validate-manifest` costs USD 0.01 and `validate-artifact` costs USD 0.05.\nMalformed requests and readiness checks do not trigger an application event\ncharge. A completed inspection whose result is `FAIL` is still a valid paid\nresult.\n\n- [ArtifactGuard Agent on Apify](https://apify.com/analytical_gratefulness/artifactguard-agent)\n- [ArtifactGuard REST/MCP Actor](https://apify.com/analytical_gratefulness/artifactguard)\n\n## Buy directly with x402\n\nThe direct endpoint returns a standards-based `402 Payment Required` response\nwith the price and payment requirements before any artifact is processed:\n\n```bash\ncurl -i \\\n  -X POST \\\n  https://artifactguard-kl4hfo6j2q-as.a.run.app/v1/validate/artifact \\\n  -H \"Content-Type: application/json\" \\\n  --data-binary @examples/x402_validate_artifact.json\n```\n\nAn x402-compatible buyer can satisfy that payment requirement and repeat the\nsame request with a payment signature. Do not place wallet private keys in a\nrequest body, repository, or log.\n\nFree discovery endpoints:\n\n- `GET https://artifactguard-kl4hfo6j2q-as.a.run.app/capabilities`\n- `GET https://artifactguard-kl4hfo6j2q-as.a.run.app/examples`\n- `GET https://artifactguard-kl4hfo6j2q-as.a.run.app/presets`\n\n## MCP\n\nThe Apify Standby Actor exposes Streamable HTTP MCP at:\n\n```text\nhttps://analytical-gratefulne--artifactguard.apify.actor/mcp\n```\n\nSupply your own Apify token as an `Authorization: Bearer ...` header in the MCP\nclient. Available tools include `validate_manifest`, `validate_artifact`, and\nthe free `verify_receipt` tool.\n\n## Verify a receipt independently\n\nInstall the single verifier dependency and pass either a receipt object or the\nfull ArtifactGuard response envelope:\n\n```bash\npython -m pip install -r requirements.txt\npython verify_receipt.py receipt-response.json\n```\n\nThe verifier retrieves only the public Ed25519 key identified by the receipt,\nrecomputes the canonical receipt hash, and verifies the signature. It never\nneeds an API token, payment credential, or private key.\n\n## Files\n\n- `examples/validate_artifact.json`: Apify Actor input.\n- `examples/x402_validate_artifact.json`: direct x402 API input.\n- `examples/validate_manifest.json`: inexpensive manifest-only Actor input.\n- `verify_receipt.py`: independent receipt hash and signature verifier.\n- `server.json`: Official MCP Registry metadata for the authenticated remote.\n\n",
  "bytes": 3588,
  "sha": "9050e9a997eb7ee5218606b48235b962d33d72db51ca2bc556ee0e99cf729c5c",
  "repo_slug": "blackcow4234-lab/blackcow4234",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_blackcow4234_lab_artifactguard_b9c01daf/readme"
}