Machine-readable builder proofs
Builder examples · ABI · API requests
Copy-paste builder examples for token gating, SIWE, loyalty, attribution, and policy-aware integrations
Builders need evidence, not marketing claims. This page publishes ABI JSON, deployment metadata, endpoint examples, and integration snippets for web3 product teams, publishers, and wallet-native communities.
Builder answer: Use the compiled ERC-721 and ERC-1155 artifacts, inspect the deployment metadata, and test each endpoint in your target environment. An available artifact proves implementation; it does not prove a production deployment.
Contract artifacts
| Resource | Purpose |
|---|---|
| TSTAccessToken.json | ERC-721 access-pass ABI and bytecode metadata for token-gated content checks. |
| TSTLoyaltyBadge.json | ERC-1155 loyalty badge ABI and bytecode metadata for contributor status checks. |
| Configured contracts JSON | Configured chain, deployer, and contract addresses. Empty values mean no deployment is declared. |
Example API requests
Safety boundary: These read-only examples use placeholders. Never paste a private key, seed phrase, recovery phrase, or unrelated wallet identifier into a request, support message, or public log.
Gate check request shape
POST /api/v1/gate-check
content-type: application/json
{"ruleId":"approved-rule","walletAddress":"<user-provided identifier>"}Loyalty status request shape
GET /api/v1/loyalty-status?walletAddress=<user-provided identifier>
JavaScript with ABI metadata
const artifact = await fetch('/artifacts/contracts/TSTAccessToken.sol/TSTAccessToken.json').then(r => r.json());
const deployment = await fetch('/data/web3/contracts.json').then(r => r.json());
console.log(artifact.abi, deployment.contracts.accessToken);Policy-aware integration
const policy = await fetch('/web3/policy/onchain-data-use.json').then(r => r.json());
if (policy.allowedReads.includes('erc721BalanceOf')) {
// proceed with a documented token-gating check
}How to verify the Web3 implementation
Fetch ABI files, inspect deployment metadata, and test endpoint responses in the target environment.
- Load ABI artifacts: Fetch the ERC-721 or ERC-1155 artifact JSON under /artifacts/contracts/.
- Check deployment metadata: Read /data/web3/contracts.json for configured chain and addresses.
- Test the deployed endpoints: Call /api/v1/gate-check and /api/v1/loyalty-status in the target environment, then apply the published policy boundaries.
Evidence, freshness, and corrections
- Written and edited by
- Rachel Julian, founder and editor
- Last reviewed
- 2026-08-13
- Readiness rule
- Scaffold means designed, not implemented. Beta means implemented with production verification pending. Live means independently verified end to end. Source code, ABI files, endpoints, or configuration never prove production availability.
- Correction path
- Report a correction or compare the capability changelog.
Source hierarchy
- Primary standards: Protocol specifications and standards bodies define what an implementation must do.
- Security guidance: Threat-model and identity guidance define controls, failure handling, and recovery expectations.
- Deployment evidence: Independent end-to-end checks establish whether a configured production capability is live.
- Editorial judgment: I apply those sources to revenue-travel decisions and state where the evidence stops.