Mapae (mapae.io)

Infra

GASOK

Delegates a scoped spending authority to an AI agent instead of the wallet itself

A payment-authority layer that hands an AI agent a bounded allowance rather than the wallet. The owner fixes the asset, the recipient, a per-payment cap, a cap per period and a validity window, and the agent pays on its own within those limits.

What makes it more than a promise is that the chain checks the limits rather than a backend. When the agent meets a 402 payment request it builds a one-time permission carrying only that payment's amount and recipient, and only transfers whose asset, cap, period and recipient fall inside the delegated scope settle on GIWA. The owner can revoke the grant at any point instead of waiting for it to expire.

GIWA is the settlement network, x402 the payment handshake, ERC-7710 the delegated authority and ERC-4337 the smart account. The site links documentation, GitHub and an Open Studio for building a grant by hand. As checked on 2026-09-01 it also linked three delegated payments actually settled on GIWA Sepolia, with the team's own note that these use test assets and do not indicate readiness for real-value use.

As of 2026-09-24 the top of the site also pitches the receiving side. A merchant can accept x402 payments on GIWA with one line of Hono middleware, and a shop with no server can use a payment URL instead.

Description from: mapae.io · @mapae_io ↗ · the project's own description

Note: The similarly named @MapaeGiwa is a separate account that presents a creator token issuance platform on GIWA and announced its own selection. The two have never mentioned each other and use different logos, so they are listed as separate projects. On 2026-09-01 this description was attached to the @MapaeGiwa entry on the view that both were one project; it was corrected on 2026-09-24 after confirming that the account linking mapae.io in its profile is @mapae_io.

Website ↗X ↗GASOK evidence ↗

This list mixes projects' own announcements, tips from others and our own research, and its accuracy is not guaranteed. Being listed is not a recommendation or endorsement, nor does it mean a project is safe from shutdowns, hacks or rug pulls. Check for yourself before taking part.

Link preview

Mapae — Limit the authority. Let the agent act.

Accept x402 on GIWA with one line of Hono middleware, or a payment URL for a shop with no server. An AI agent pays within the boundaries its owner set — asset, amount, period, recipient — and the owner can revoke at any time.

mapae.io ↗

The project's own Open Graph image and text.

About on X

@mapae_io

Bounded authority for autonomous payments on GIWA — the agent gets limits, not your wallet · A GASOK project by @GIWA_by_Upbit

Followers: 4
Following: 1
Posts: 9

Joined Aug 2026mapae.io ↗

GASOK Phase 3

Status: Selected
Evidence tier: Self-announced
Evidence: View source ↗

Based on a public statement by the project itself or a credible third party. GIWA has never published an official roster. Phase 3 is also an ongoing stage, so this means admission to it rather than completion.

What is GASOK Phase 3?

GASOK is Dunamu and Upbit's builder program for GIWA, an incubation running seven months or more. Phase 3 (Aug–Nov 2026) is the "market readiness & launch" stage, aiming at testnet user metrics and a private mainnet deployment. There are five tracks: DeFi/RWA, Consumer/Social, GIWA-Native, AI/Web3, and Mass Adoption.

What teams admitted to GASOK Phase 3 receive

Engineering and productization support from the GIWA team, plus industry advisors
Seoul office space if needed, and press and media support
A shot at the KBW 2026 Showcase (the top team in each track, five in all)
A $20K grant if picked at the Finalist Demo Day (date not yet announced), then up to $80K more tied to KPIs

The similarly named @MapaeGiwa is a separate account that presents a creator token issuance platform on GIWA and announced its own selection. The two have never mentioned each other and use different logos, so they are listed as separate projects. On 2026-09-01 this description was attached to the @MapaeGiwa entry on the view that both were one project; it was corrected on 2026-09-24 after confirming that the account linking mapae.io in its profile is @mapae_io.

Something wrong or missing on this project? Tell us on Telegram ↗ Partnership enquiries reach us the same way.