IAM Policy Diff

Compare two IAM policies and report what the change grants or removes. The comparison is over action-and-resource pairs rather than over statements, so a refactor that splits one statement into three reports no change. A newly written pair already covered by a broader unconditioned pattern is noted rather than reported, since nothing new is granted. A removed Deny is reported as a widening even when no Allow changed, because a Deny overrides every Allow.

Otherofflineeip155:8453Exactvia cdp
IamAccess controlChange reviewLeast privilegeDeveloper tooling
Settlements · 30d
219↓ 44%
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days.
$25.35
Verified settled volume
256 settlements proven x402 by their on-chain EIP-3009 marker.
$0.190
Listed price
As published in the catalog. Always read the live 402 before paying.
1
Calls · 30d
Upstream's own call count for this endpoint, not ours.
1
Unique payers · 30d
Last called 2026-10-04 08:29Z
—
Upstream on-chain volume
Reported by the source catalog.
Paid to
0x25e8245f07d5e4873987293dad666afbe56a9608

The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.

Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Provider

The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.

Accepts

The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.

0.19USDC≈ $0.19 USD
on Base · exact scheme

Pay 0.19 USDC on Base to 0x25e8…a9608. The signed payment is good for 1 minute.

USD Coin contract
0x8335…02913
Payment window
1 minute
As published
190000 smallest units
The catalog’s raw entry
[
  {
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "extra": {
      "name": "USD Coin",
      "version": "2"
    },
    "payTo": "0x25e8245f07d5e4873987293dad666afbe56a9608",
    "amount": "190000",
    "scheme": "exact",
    "network": "eip155:8453",
    "maxTimeoutSeconds": 60
  }
]

Extensions

{
  "bazaar": {
    "info": {
      "input": {
        "body": {
          "after": "{\n \"Version\": \"2012-10-17\",\n \"Statement\": [\n  {\n   \"Sid\": \"ReadExports\",\n   \"Effect\": \"Allow\",\n   \"Action\": [\n    \"s3:GetObject\"\n   ],\n   \"Resource\": [\n    \"arn:aws:s3:::exports/*\"\n   ]\n  },\n  {\n   \"Sid\": \"WriteExports\",\n   \"Effect\": \"Allow\",\n   \"Action\": [\n    \"s3:PutObject\"\n   ],\n   \"Resource\": [\n    \"arn:aws:s3:::exports/*\"\n   ]\n  }\n ]\n}",
          "before": "{\n \"Version\": \"2012-10-17\",\n \"Statement\": [\n  {\n   \"Sid\": \"ReadExports\",\n   \"Effect\": \"Allow\",\n   \"Action\": [\n    \"s3:GetObject\"\n   ],\n   \"Resource\": [\n    \"arn:aws:s3:::exports/*\"\n   ]\n  },\n  {\n   \"Sid\": \"DenyProduction\",\n   \"Effect\": \"Deny\",\n   \"Action\": [\n    \"s3:DeleteObject\"\n   ],\n   \"Resource\": [\n    \"arn:aws:s3:::production/*\"\n   ]\n  }\n ]\n}"
        },
        "type": "http",
        "method": "POST",
        "bodyType": "json"
      },
      "output": {
        "type": "json",
        "example": {
          "limits": {
            "maxEnvBytes": 131072,
            "maxFindings": 500,
            "maxPlanBytes": 4194304,
            "maxResources": 5000,
            "maxStatements": 500,
            "maxPolicyBytes": 262144
          },
          "passed": false,
          "widens": true,
          "narrows": false,
          "complete": true,
          "findings": [
            {
              "code": "ALLOW_ADDED",
              "pair": "s3:PutObject on arn:aws:s3:::exports/*",
              "detail": "s3:PutObject on arn:aws:s3:::exports/* is newly allowed with no Condition."
            },
            {
              "code": "DENY_REMOVED",
              "pair": "s3:DeleteObject on arn:aws:s3:::production/*",
              "detail": "s3:DeleteObject on arn:aws:s3:::production/* was denied and is not. A Deny overrides every Allow, so removing one can widen the policy even when no Allow changed."
            }
          ],
          "equivalent": false,
          "request_id": "example-request",
          "service_id": "iam_policy_diff",
          "assumptions": [
            "The comparison is over action-and-resource pairs rather than over statements, because the pair is what grants something. A refactor that splits one statement into three therefore reports no change, wh...",
            "A newly written pair already covered by a broader unconditioned pattern is noted rather than reported as a widening, since nothing new is granted.",
            "A removed Deny is reported as a widening even when no Allow changed, because a Deny overrides every Allow."
          ],
          "limitations": [
            "The two policy documents supplied. What they are attached to, and which other policies apply, are outside this. Not a security assessment.",
            "equivalent is true only when nothing was granted, nothing was removed and nothing was left uncompared."
          ],
          "observed_at": "2026-10-02T00:00:00.000Z",
          "not_examined": [],
          "finding_count": 2,
          "service_version": "1.0.0",
          "findings_by_code": {
            "ALLOW_ADDED": 1,
            "DENY_REMOVED": 1
          },
          "after_statement_count": 2,
          "after_allow_pair_count": 2,
          "before_statement_count": 2,
          "before_allow_pair_count": 1
        }
      }
    },
    "schema": {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "input"
      ],
      "properties": {
        "input": {
          "type": "object",
          "required": [
            "type",
            "method",
            "bodyType",
            "body"
          ],
          "properties": {
            "body": {
              "type": "object",
              "required": [
                "before",
                "after"
              ],
              "properties": {
                "after": {
                  "type": "string",
                  "maxLength": 262144
                },
                "before": {
                  "type": "string",
                  "maxLength": 262144
                }
              },
              "additionalProperties": false
            },
            "type": {
              "type": "string",
              "const": "http"
            },
            "method": {
              "enum": [
                "POST"
              ],
              "type": "string"
            },
            "bodyType": {
              "enum": [
                "json",
                "form-data",
                "text"
              ],
              "type": "string"
            }
          },
          "additionalProperties": false
        },
        "output": {
          "type": "object",
          "required": [
            "type"
          ],
          "properties": {
            "type": {
              "type": "string"
            },
            "example": {
              "type": "object"
            }
          }
        }
      }
    }
  }
}

Provenance

Seen in the source catalog
2026-10-04 08:29Z
Last indexed by Roundhouse
2026-10-05 00:20Z
Last enriched (probe, favicon, geo)
2026-10-05 00:46Z
x402 version
2
Max timeout
60s
Liveness probe
HTTP 0
Report

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.

GET api.roundhouseai.io/v0/endpoints

No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days. Verified volume counts only settlements with an on-chain EIP-3009 marker.

Open skill.md
Show the prompt
Using Roundhouse, look up the x402 service IAM Policy Diff and tell me whether it is
worth paying: what a call costs, whether the endpoint answered when last probed, and what
its payment record actually shows.

curl -s 'https://api.roundhouseai.io/v0/endpoints?q=IAM%20Policy%20Diff'
curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>'

Then call it: read the price from the live 402 at https://api.zfinia.com/x402/v1/iam-policy-diff, never from
a cached figure, and pay with an x402 client.

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at
GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at
https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.