TAP v1.0 — March 2026

Teleport Access Protocol

An internet-native payment protocol for accessing spatial data using PORT tokens. HTTP 402 meets blockchain settlement.

Read Whitepaper
Why TAP Exists

The payment layer spatial data needs

The Problem
  • Credit card friction — KYC, minimums, chargebacks
  • No machine-to-machine payment standard
  • Minimum transaction fees kill micropayments
  • Settlement takes 2–5 business days
  • Cross-border payments are slow and expensive
TAP Solution
  • HTTP 402 — the payment-required status code, finally used
  • No KYC, no accounts — just a wallet address
  • Instant settlement on-chain in under 15 seconds
  • Agent-native — AI and IoT can pay programmatically
  • Pay-per-call pricing from $0.002 per request

HTTP 402 “Payment Required” was reserved in 1997 for “future use.” Nearly three decades later, TAP finally gives it a purpose — a native payment layer for the internet that lets any client pay for any API call with a single token transfer.

Protocol Flow

Seven steps to spatial data

From initial request to data delivery — the complete TAP handshake sequence.

1
HTTP Request(no payment)
2
402 Payment Required+ pricing (USDC / PORT)
3
Signed payment(PORT / USDC / ETH)
4
Verify & settleon-chain
5
Confirmation
6
Payment verified
7
API Response(data / 360 content)
Architecture

System architecture

Five layers from client to chain, with TAP middleware handling payment verification transparently.

Teleport Access Protocol — System ArchitectureWeb AppAI AgentMobile AppMCP ServerTAP Middleware — Payment Gate + Rate Limiter + Auth360 Images API360 Video APIDatasets APIGeospatial APITAP Verifier / SettlementEthereum (PORT ERC-20)Base (PORT Bridge)Solana / PolygonFrom client applications through middleware to blockchain settlement
Token Economy

PORT token economy

A circular economy where consumers, creators, treasury, and governance interact through PORT.

PORTConsumersPay PORT for API accessCreatorsEarn PORT for spatial dataTreasuryProtocol sustainabilityGovernanceVote on protocol upgrades

PORT Discount Schedule

PeriodDiscountNote
Year 150%Early adopter maximum discount
Year 240%Growth phase discount
Year 335%Maturity phase
Year 430%Stabilization
Year 5+25%Long-term floor rate
Distribution

Token distribution

10B PORT Total Supply
Treasury30%
Creator Rewards20%
Team & Advisors15%
API Demand Pool10%
Community10%
Strategic Reserve10%
Liquidity5%
Roadmap

Launch sequence

Four phases from silent accumulation to full decentralized governance.

Silent Accumulation

0 - 6 months

Build treasury reserves, early creator onboarding, protocol development

Token Generation

6 - 9 months

PORT token launch, initial distribution, staking activation

Liquidity Launch

9 - 12 months

DEX listings, liquidity pools, market maker partnerships

Scale & Governance

12 - 18 months

DAO governance, multi-chain expansion, enterprise adoption

Pricing

API pricing

Pay per call in USDC or get a discount with PORT tokens.

EndpointUSDCPORT
/spaces/:id$0.0021.5 PORT
/spaces/feed$0.0053.5 PORT
/spaces/nearby$0.0032 PORT
/locations/:id$0.0053.5 PORT
/locations/feed$0.0053.5 PORT
/captures/:id$0.0107 PORT
/analytics/overview$0.0085.5 PORT
/search$0.0107 PORT
/embeddings$0.01510 PORT
Integration

Start building in minutes

server.ts
import { tapMiddleware } from '@teleport/tap';

app.use(tapMiddleware({
  contractAddress: '0x...PORT',
  chains: ['ethereum', 'base'],
  discountRate: 0.50,
}));
client.ts
import { TAPClient } from '@teleport/tap-client';

const tap = new TAPClient({
  wallet: '0x...',
  preferToken: true,
});

// Auto-handles 402 → pay → retry
const space = await tap.get('/spaces/abc');
Multi-Chain

One protocol, multiple chains

TAP verifies payment proofs across Ethereum, L2s, and Solana through a unified bridge hub.

TAP BridgeHubEthereumNativeBaseBridgePolygonBridgeSolanaPlanned
ChainSpeedGas CostStatus
Ethereum~15s$2-50Native
Base~2s<$0.01Live
Polygon~2s<$0.01Live
Solana~400ms<$0.001Planned
Comparison

TAP vs traditional payments

FeatureTAP + PORTTraditional
Account RequiredNoYes
Minimum Payment$0.002$25+
Transaction Fees<$0.012.9% + $0.30
TOKEN DiscountUp to 50%None
Settlement Time<15 seconds2-5 business days
AI Agent SupportNativeNone
MicropaymentsPer-call pricingNot viable
Cross-BorderInstant, globalRestricted
Integration Effort1 middleware lineWeeks of dev
Get Started

Build with TAP

Read the whitepaper, integrate the SDK, and start accepting PORT payments for your spatial data API.

Download Whitepaper