Local QUIC
Connect a QUIC client to the local agent with the correct ALPN and certificate settings.
Connect to UDP 127.0.0.1:4433, or your configured listen.quic address. Use the hosted QUIC payloads and reply format with these local settings.
Connection settings
| Setting | Value |
|---|---|
| Address | listen.quic, default 127.0.0.1:4433 |
| TLS | TLS 1.3 |
| ALPN | zerocopy-swqos/1 |
| Server certificate | Self-signed for localhost, new at each agent start |
| Client certificate | Optional and ignored |
| Idle timeout | 30 seconds; send keep-alive pings to hold a quiet connection open |
| Concurrent streams | Up to 64 bidirectional and 64 unidirectional per connection |
| Connections | Up to 4,096 in total |
The local certificate
The agent uses a self-signed localhost certificate that changes at each start. Use localhost as the server name and configure your client to accept that certificate for this loopback connection.
If your QUIC library requires disabling certificate verification, restrict that exception to the local listener. Keep verification enabled for every hosted endpoint.
Authentication
The local listener uses the executable's license, not a client certificate or API key. Keep it on loopback so other hosts cannot submit on your account.
Sending
| Channel | Through the agent |
|---|---|
| Datagram | A transaction or bundle payload, with no reply |
| Unidirectional stream | A transaction or bundle payload, with no reply |
Bidirectional stream, kind 0x01 | A transaction with a reply. Flag 0x01 requests preflight at processed commitment. |
Bidirectional stream, kind 0x03 | A bundle with a reply |
Replies use the hosted reply codes and JSON details. The agent adds the rejections listed for local HTTP. What an accepted reply means explains code 0 from the agent.
A send without a reply that the agent refuses, for example for an insufficient tip, is dropped without notice. Use bidirectional streams while you integrate, so you see every rejection.