# 404KIN FIELD: public-mint integration

The public stage was observed open on Ethereum; **the artwork was revealed by the creator on 18 September 2026**. [agent.json](agent.json) records timestamps and source scope. The latest fixed-block observation was **2 minted of 10,000 at Ethereum block 26004378 on 2026-09-18 12:26:47 UTC**. The [successful two-token public mint](https://etherscan.io/tx/0xf5dc419633bf7220bef65a4ac12903de7aa43d2d34841e8c91606d59e0122fee) came from a project-funding-related wallet. This demonstrates that transaction's direct-public route, not independent buyer demand or AI participation. AI identity remains unknown; the count is a snapshot.

## Direct public route

The public configuration snapshot is **0.001 ETH per mint, cumulative limit 2 for the recipient, maximum supply 10,000**. The observed window is **2026-09-17 15:51:28 UTC through 2026-09-30 15:51:28 UTC**. Gas is extra. Terms and eligibility need fresh reads before every purchase.

The exact NFT, SeaDrop and platform fee-recipient addresses are in [api-integration.json](api-integration.json). A direct public mint calls **SeaDrop**, not the NFT contract or creator Safe:

```solidity
mintPublic(address nftContract, address feeRecipient, address minterIfNotPayer, uint256 quantity)
```

Selector: `0x161ac21f`. Parameter order is exactly as shown. The recorded `feeRecipient` is the allowed OpenSea platform recipient, separate from creator payout. A zero `minterIfNotPayer` makes the caller the recipient; a different recipient requires payer-permission checks. Transaction value is the current price in integer wei multiplied by quantity; the recorded 1,000 bps platform fee is split from that mint value, not added again. None of these descriptions supplies executable calldata or authorizes a transaction.

A buyer-controlled client needs chain ID 1; the expected SeaDrop and NFT addresses; fresh `getPublicDrop`, fee-recipient allowance, payout, supply and recipient `getMintStats` reads; the actual remaining allowance; and an exact target/calldata/value simulation from its own payer. Contract-wallet recipients also need receiver compatibility. Simulation does not reserve a token or lock a future price. Only the buyer's own authorized signer can review and send a transaction.

The successful observed transaction encoded the four public-mint arguments and an additional four-byte suffix, `0x3d958fe2`. Its purpose is not established here. The record is evidence of those actual bytes, not permission to accept arbitrary appended calldata or skip decoding and simulation.

## OpenSea API path

[Drop lookup](https://docs.opensea.io/reference/get_drop_by_slug) uses `GET /api/v2/drops/404kin-field`. [Mint-data construction](https://docs.opensea.io/reference/build_drop_mint_transaction) uses `POST /api/v2/drops/404kin-field/mint` with the buyer's public `minter` and desired integer `quantity`. These APIs require the caller's own API key; no key is supplied or requested here. The builder returns transaction data and does not sign or broadcast. At 2026-09-18 00:53:28 UTC, actual project-specific requests returned HTTP 200 for drop lookup and one unsigned quantity-one mint construction. The response used `to`, `data`, `value`, and `chain`; decoding matched the expected direct `mintPublic` target, NFT, fee recipient, requested recipient, quantity and 0.001 ETH value. The trailing four bytes matched the earlier successful transaction but their purpose remains unestablished. No simulation, gas estimate, signature or broadcast was performed. This is not universal buyer eligibility or transaction approval. See [scoped API evidence](api-verification.json).

The backend may select the first eligible stage. Returned `target`, decoded calldata, amount and route must be checked against current state; response field names must follow the actual schema. Direct `mintPublic` through an Ethereum provider does not require an OpenSea API key, though it still requires correct state, simulation and the buyer's signer.

## Signed route has different bounds

The observed configuration also permits a platform signer to authorize a wider signed-mint envelope: minimum permitted price 0, wallet-limit parameter up to 10,000 and an end bound one day later. **The public 0.001 ETH / two-per-wallet conditions are not guaranteed across every route.** The proposed tightening has not been executed; signer ownership and checkout compatibility have not been established.

Those bounds still require a valid signer authorization. They do not prove that anyone can mint for free without a signature, that a key is compromised, or that funds were stolen. A buyer integration receiving a signed-route transaction needs separate review and must not inherit public-route assumptions.

## Artwork and reveal

The creator signed [setBaseURI](https://etherscan.io/tx/0xb90c902f76aad899e01c9cc71ca8c115c6a712dd585c938663fea21e05028aea) on 18 September 2026, advancing the prior after-sale plan. The receipt succeeded, the cap remains 10,000 and the current minted tokenURIs for IDs 1 and 2 returned their matching original V4.1 metadata and SVGs. [Dated reveal evidence](/api/nft/v4-1/reveal.json) records the scope. Marketplace caches may lag the chain.

Primary allocation is sequential. A selected catalog artwork or trait is **not** reserved; intervening transactions can change received IDs. The 10,000-item catalog preserves original artwork order, but it is not a selected-image purchase flow or commercial-use licence.

The current base URI is `https://field-404kin.cv5gyqnshz.chatgpt.site/api/nft/v4-1/metadata/`. Append the unpadded decimal token ID, with no file extension, for example `1`; the actual contract tokenURI is authoritative and unminted IDs can revert. This is operator-maintained HTTPS, not an IPFS directory. [Rights and hosting](RIGHTS_AND_HOSTING.md) describes continuing availability limits. Collectible art conveys no financial rights, profit entitlement or guaranteed return.