When an autonomous agent is about to release USDC, it screens the payee, the screen says ALLOW — and it's wrong. With every tool on the market, the agent is left holding an unsigned JSON blob it can't prove anyone stood behind.
PayPerByte (machine name: BYTE Library) sells the missing piece: a signed, neutral, reproducible go/no-go verdict an agent buys per call and can prove after the fact. The flagship is the Address Reputation Oracle — POST a (domain, receiving address, amount, chain) and get back a signed ALLOW / WARN / BLOCK for $0.05, before the funds move. Same model backs 22 first-party feeds and oracles: markets, DeFi, security advisories, CVE/package facts, legal statutes, and more.
How it pays: keyless x402 — the agent's wallet signs an EIP-3009 USDC transfer; no API key, no signup, no token. Pay-per-call settles in real USDC on Base mainnet (eip155:8453) through a CDP-discoverable facilitator.
Why it's trustworthy: every paid response carries an on-chain EIP-712 PayloadAttestation, returned in an X-BYTE-Attestation receipt. The agent recomputes the hash and recovers the signer before acting — verify-before-act. If it doesn't match, don't act on it.
Honest about the rails: the x402 pay-per-call rail is live on Base mainnet. The EIP-712 signing domain and the on-chain subscribe layer are anchored on Arbitrum (chainId 421614); a mainnet attestation anchor is pending an external security audit. The signing namespace is fixed regardless of which rail you pay on — by design.
No token. No external-traction claims: the loop is dogfooded and operated as live infrastructure; whether builders pay for signed over free-unsigned is the open question we're testing in the open.
Discoverable: npm `byte-mcp-server` (15 MCP tools), the official MCP registry (`io.github.0rkz/byte-protocol`), an A2A agent card, x402scan and x402scout, and an ERC-8004 identity. Curl the 402 challenge yourself — the demo is the pitch.
Rating Reviews
Rating is calculated based on
1
review and is evolving.
Pros: The company culture at BYTE felt supportive and collaborative, especially within smaller teams. I appreciated the opportunity to gain experience in the direct-to-consumer (DTC) and healthcare technology space. There were chances to take on new responsibilities and learn about various marketing functions, which was great for professional development.
Cons: Being a fast-paced startup environment, workload could become intense, particularly during peak periods or product launches. Communication regarding broader company strategy or role changes could sometimes be a bit unclear, leading to occasional confusion. The career progression path wasn't always well-defined.
Advice to Management: Consider creating more structured career development paths and ensuring consistent communication about company direction and role expectations, especially during periods of change or growth.
Show more
What's the typical salary range for a software engineer at BYTE, a mid-sized tech company in Austin?
Based on what I've seen and heard, salaries for software engineers at BYTE in Austin tend to be competitive within the mid-sized tech market, with entry-level roles starting around $80k and experienced engineers potentially earning over $120k.
US
