How to connect to The Trinity Beast Infrastructure via PrivateLink (TCP) and VPC Peering (UDP).
Our Philosophy — We Receive Freely, We Give Freely
The Trinity Beast exists because of generosity. Coinbase, Bitstamp, Kraken, Gate.io, Crypto.com, and OKX provide their real-time price feeds to us at no cost. They ask nothing in return. That generosity is the foundation of everything we have built.
We believe the right response to that kind of generosity is to pass it forward. If your AWS application needs live cryptocurrency prices, we will provide them to you — free of charge, with no rate limiting, no monthly caps, and no billing. Not because we expect something back, but because that is how the AWS community should work.
Your API key comes with unlimited access and direct container connectivity via AWS PrivateLink or VPC Peering for sub-2ms latency. No public internet, no load balancer hops, no throttling. The same infrastructure our paying subscribers use — but at no cost to you.
Beyond the technology, 100% of the subscription revenue that The Trinity Beast generates goes directly to Cross Power Ministries of Pakistan, funding freedom from brick kiln debt bondage. When you partner with us, you are part of something larger than an API.
If you need direct, low-latency access to The Trinity Beast — bypassing the public ALB and the internet — you have two connection paths depending on the protocol you need:
| Protocol | Connection Method | Ports | Consumption Model | What You Do |
|---|---|---|---|---|
| TCP (LPO + LRS) | PrivateLink | 8080 (LPO), 9090 (LRS) | Request/response OR real-time WebSocket push feed | You create a VPC endpoint; we approve it |
| UDP (LPO + LRS) | VPC Peering → NLB | 2679 (LPO), 2680 (LRS) | Request/response — lowest possible latency, zero overhead | You request peering; we accept and route |
Why two methods? AWS PrivateLink does not support UDP. If you're a TCP partner, PrivateLink gives you the cleanest experience — no CIDR coordination, no route table changes — and you can choose between polling or a persistent WebSocket feed. If you need UDP, VPC Peering is required. It involves more setup on both sides, but delivers raw UDP speed — datagrams routed through the NLB with zero measurable overhead.
These are the ports your infrastructure team should monitor. If any of them go silent, your price feed is down.
| Port | Protocol | Service | Connection Method | What It Delivers | Health Signal |
|---|---|---|---|---|---|
| 8080 | TCP | LPO — Live Price Oracle | PrivateLink | Price queries (request/response) + WebSocket real-time feed (/ws/prices) |
GET /health → 200 |
| 9090 | TCP | LRS — Ledger Reporting Service | PrivateLink | Usage reports, transaction history, analytics | GET /health → 200 |
| 2679 | UDP | LPO — Live Price Oracle | VPC Peering → NLB | Price queries — lowest latency, zero overhead | Send a probe, expect a UME reply within 100 ms |
| 2680 | UDP | LRS — Ledger Reporting Service | VPC Peering → NLB | Usage reports via UDP — same data as TCP, faster transport | Send a probe, expect a UME reply within 100 ms |
Monitoring guidance:
/health every 30 seconds. A non-200 response means the backend is unhealthy — escalate immediately.{"asset":"BTC","api_key":"YOUR_KEY"}) every 60 seconds. No reply within 3 seconds means your path is broken./ws/prices on port 8080): If no price update arrives for 60 seconds after subscribing to a liquid asset (BTC, ETH), your connection is stale — reconnect.status_code == 200 and error == "" — anything else is a fault.Verified live — August 24, 2026: Both PrivateLink ports (8080 and 9090) carried real requests through a VPC endpoint to the internal NLB, returning valid UME responses with live exchange data. The path is production-ready.
PrivateLink creates a private endpoint in your VPC that routes directly to our internal TCP NLB. Traffic stays on the AWS backbone the whole way — you never see our VPC CIDR or container IPs, and we never see yours.
The Trinity Beast PrivateLink Service (already live):
| Attribute | Value |
|---|---|
| Service Name | com.amazonaws.vpce.us-east-2.vpce-svc-0147410454a727b3f |
| Ports | TCP 8080 (LPO), TCP 9090 (LRS) |
| Acceptance | Required — we approve every connection request individually |
1 Create a VPC Interface Endpoint in your VPC, pointing at our service name:
aws ec2 create-vpc-endpoint \ --vpc-id vpc-YOUR_VPC_ID \ --service-name com.amazonaws.vpce.us-east-2.vpce-svc-0147410454a727b3f \ --vpc-endpoint-type Interface \ --subnet-ids subnet-YOUR_SUBNET \ --security-group-ids sg-YOUR_SG \ --region us-east-2
2 Wait for us to accept — your connection request will show as pendingAcceptance until we approve it, typically within one business day.
3 Configure your endpoint's security group to allow outbound TCP on ports 8080 and 9090, and inbound from your application's CIDR on those same ports.
4 Connect using the endpoint DNS:
# LPO price query via PrivateLink (request/response)
curl http://vpce-XXXX.vpce-svc-0147410454a727b3f.us-east-2.vpce.amazonaws.com:8080/price?asset=BTC&api_key=YOUR_KEY
# LRS report via PrivateLink (Authorization: Bearer header required)
curl -H "Authorization: Bearer YOUR_KEY" \
http://vpce-XXXX.vpce-svc-0147410454a727b3f.us-east-2.vpce.amazonaws.com:9090/reports/usage
# Real-Time WebSocket Feed (persistent connection — prices pushed as they arrive)
wscat -c "ws://vpce-XXXX.vpce-svc-0147410454a727b3f.us-east-2.vpce.amazonaws.com:8080/ws/prices?api_key=YOUR_KEY"
# Then subscribe: {"subscribe": ["BTC","ETH","SOL"]}
# Prices flow continuously — no polling required
flowchart TD
A[You create a VPC Interface Endpoint] --> B[Connection shows pendingAcceptance]
B --> C[The Trinity Beast approves the connection]
C --> D[Endpoint becomes available]
D --> E[You connect using the endpoint DNS on ports 8080 / 9090]
E --> F[Traffic routes over the AWS backbone]
F --> G[NLB load-balances to a healthy container]
G --> H[You receive a UME response]
style A fill:#1e3a5f,stroke:#60a5fa,color:#e2e8f0,stroke-width:2px
style B fill:#334155,stroke:#94a3b8,color:#e2e8f0,stroke-width:2px
style C fill:#4a2800,stroke:#FF9900,color:#e2e8f0,stroke-width:2px
style D fill:#064e3b,stroke:#10b981,color:#e2e8f0,stroke-width:2px
style E fill:#1e3a5f,stroke:#60a5fa,color:#e2e8f0,stroke-width:2px
style F fill:#334155,stroke:#94a3b8,color:#e2e8f0,stroke-width:2px
style G fill:#334155,stroke:#94a3b8,color:#e2e8f0,stroke-width:2px
style H fill:#064e3b,stroke:#10b981,color:#e2e8f0,stroke-width:2px
You can open a persistent WebSocket connection at /ws/prices?api_key=KEY on port 8080 and receive real-time price updates from the same exchange feeds that power the entire system. No polling, no intervals — prices arrive the instant they're received from the 6 exchanges.
| Direction | Message | Purpose |
|---|---|---|
| You → Us | {"subscribe": ["BTC","ETH","SOL"]} | Subscribe to assets |
| You → Us | {"unsubscribe": ["DOGE"]} | Remove assets |
| You → Us | {"ping": true} | Keepalive |
| Us → You | {"type":"price","asset":"BTC","price":97432.51,"source":"coinbase-ws"} | Real-time price update |
| Us → You | {"type":"subscribed","assets":["BTC","ETH","SOL"]} | Subscription confirmation |
| Us → You | {"type":"pong"} | Keepalive response |
Available assets: GET /ws/assets — returns all 360 prewarmed assets across 6 exchanges. No auth required.
VPC Peering connects your VPC to ours. Traffic routes between the two VPCs using private IPs. You send UDP datagrams to our NLB's static private IP — Layer 4 pass-through with zero measurable overhead. The NLB routes to healthy containers automatically, surviving deployments and scaling events without any changes on your end.
NLB zero overhead — proven: Stress testing confirmed that UDP through the NLB matches UDP direct-to-container within measurement noise. You get stable addressing with no performance penalty.
Requirement: Your VPC CIDR must not overlap with 10.0.0.0/16 (our VPC). Common non-overlapping CIDRs: 172.16.0.0/16, 192.168.0.0/16, 10.1.0.0/16.
1 Request a VPC Peering connection to our VPC:
aws ec2 create-vpc-peering-connection \ --vpc-id vpc-YOUR_VPC_ID \ --peer-owner-id 211998422884 \ --peer-vpc-id vpc-03deaddb7083cd59c \ --peer-region us-east-2 \ --region YOUR_REGION
2 Wait for us to accept the peering request, typically within one business day.
3 Add a route in your route table pointing to The Trinity Beast VPC:
aws ec2 create-route \ --route-table-id rtb-YOUR_RT \ --destination-cidr-block 10.0.0.0/16 \ --vpc-peering-connection-id pcx-XXXXXXXXXXXX \ --region YOUR_REGION
4 We add a matching route to your CIDR and open our security group for UDP 2679/2680 from your address range — no action needed on your end for this step.
5 Send UDP queries to the NLB private IP we provide you:
# UDP LPO price query (Python example)
import socket, json
sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
payload = json.dumps({"asset": "BTC", "api_key": "YOUR_KEY"})
sock.sendto(payload.encode(), ("NLB_PRIVATE_IP", 2679))
data, _ = sock.recvfrom(4096)
response = json.loads(data)
print(json.dumps(response, indent=2))
The NLB IP is static — it survives container deployments, scaling events, and AZ failovers on our end. You never need to update it or add reconnection logic.
flowchart TD
A[You request VPC Peering to The Trinity Beast VPC] --> B[The Trinity Beast accepts the peering connection]
B --> C[You add a route to 10.0.0.0/16]
C --> D[The Trinity Beast adds a route to your CIDR]
D --> E[The Trinity Beast opens its security group for your CIDR]
E --> F[You send a UDP datagram to the NLB private IP]
F --> G[NLB passes it through to a healthy container]
G --> H[You receive a UME response datagram]
style A fill:#1e3a5f,stroke:#60a5fa,color:#e2e8f0,stroke-width:2px
style B fill:#4a2800,stroke:#FF9900,color:#e2e8f0,stroke-width:2px
style C fill:#1e3a5f,stroke:#60a5fa,color:#e2e8f0,stroke-width:2px
style D fill:#4a2800,stroke:#FF9900,color:#e2e8f0,stroke-width:2px
style E fill:#4a2800,stroke:#FF9900,color:#e2e8f0,stroke-width:2px
style F fill:#1e3a5f,stroke:#60a5fa,color:#e2e8f0,stroke-width:2px
style G fill:#334155,stroke:#94a3b8,color:#e2e8f0,stroke-width:2px
style H fill:#064e3b,stroke:#10b981,color:#e2e8f0,stroke-width:2px
| Resource | Value |
|---|---|
| The Trinity Beast VPC ID | vpc-03deaddb7083cd59c |
| The Trinity Beast VPC CIDR | 10.0.0.0/16 |
| The Trinity Beast AWS Account | 211998422884 |
| Region | us-east-2 (Ohio) |
| TCP PrivateLink Service Name | com.amazonaws.vpce.us-east-2.vpce-svc-0147410454a727b3f |
| TCP NLB (internal) | Trinity-Beast-TCP-NLB |
| UDP NLB (static IP) | Trinity-Beast-UDP-NLB — Layer 4 pass-through, zero overhead |
| LPO TCP Port | 8080 |
| LRS TCP Port | 9090 |
| LPO UDP Port | 2679 |
| LRS UDP Port | 2680 |
| WebSocket Feed | /ws/prices?api_key=KEY (port 8080, via PrivateLink) |
| Available Assets | GET /ws/assets (no auth — lists all subscribable assets across 6 exchanges) |
| LPO Authentication | api_key query parameter |
| LRS Authentication | Authorization: Bearer YOUR_KEY header |
Behind the scenes, The Trinity Beast Command Center gives our team a dedicated Partner Management widget for reviewing and approving applications. When your application comes in, this is the tool that generates the exact commands our team runs to connect you.
The widget also gives our team a Partners tab for viewing every connected partner, a Pending Approvals tab for accepting PrivateLink and VPC peering requests, and a Security Groups tab for managing UDP access CIDRs.
Approval is not just a status flip. The moment your application is marked approved, we automatically provision your API key and email it to you — you can start making requests without any further manual step on either side.
What you receive: a live API key scoped to the partner tier (unlimited access, LRS reporting included free, no billing), and a welcome email with an authenticated 72-hour magic-link that logs you directly into your Account Dashboard — no separate login step required. We give you 72 hours instead of the normal 15-minute magic link, since you may not open the email right away. That email also includes both the TCP (PrivateLink) and UDP (VPC Peering) instructions from Sections 3 and 4.
LRS Reports are included free for your Partner-tier account by policy — no addon purchase required. Your Account Dashboard sidebar shows a Reports link under the Partner section, taking you to the same LRS Reports panel (date-range filtering, 4-format export) available to paying subscribers.
You can configure a specific watchlist of assets rather than pulling from the full prewarmed catalog on every call. Your Account Dashboard's Partner Connection panel gives you a chip-picker for this. Your watchlist is stored on your key record and is there for your own reference — it does not restrict which assets you can actually query, since Partner access is unlimited by policy.