shredstream.sh endpoint reference
Find every documented web, checkout, verification, and live-delivery endpoint together with its protocol and known port behavior.
Endpoint inventory
shredstream.sh is a pushed raw-UDP service. A customer does not open a persistent connection to a provider stream endpoint. The customer exposes a destination, verifies control of it, and receives datagrams from the documented sender.
UDP delivery contract
One UDP datagram carries one raw shred. The service does not add a framing connection, reorder packets, retransmit missing packets, or slow the sender when the receiver falls behind.
Verification endpoint behavior
The verification path is the registered customer IPv4 address and UDP port. The challenge remains valid for 600 seconds. Its first line is SHRED-FANOUT-VERIFY/1. Both the challenge and later live traffic originate from 64.130.40.90.
The remainder of the challenge wire format, resend pacing, maximum resend count, source UDP port, and delay from accepted verification to first live packet are not currently specified.
Live receive endpoint behavior
Bind the configured destination port before verification and keep it bound for streaming. Permit UDP from 64.130.40.90. Allocate a receive slot of at least 1,228 bytes and use the returned datagram length rather than assuming every packet is the measured 1,216-byte mean.
There is no TCP, gRPC, or WebSocket delivery endpoint in the documented product facts. There is also no receiver URL, hostname, multicast group, session identifier, ordered stream number, or reconnect operation in the raw UDP contract.
Web endpoints
The public site is https://shredstream.sh and checkout is https://checkout.shredstream.sh. Their URL schemes establish HTTPS. A nonstandard network port, IP allowlist, public API base URL, API version, and machine-authentication contract are not currently specified in the product facts.
Do not derive an integration endpoint from internal application paths. Only documented public contracts belong in receiver configuration.
Questions
- What host does a receiver connect to for the live stream?
- There is no documented provider host that the receiver connects to. Delivery is pushed over UDP from 64.130.40.90 to the customer-configured IPv4 address and destination port. The receiver binds that local port, permits the fixed source, completes verification, and then accepts raw datagrams.
- Which UDP port does shredstream.sh use?
- The destination UDP port is configured for the customer destination. The product facts do not currently specify its allowed numeric range or the service source UDP port. Firewall rules should therefore match source IP 64.130.40.90, UDP, and the configured destination port without constraining the source port.
- Does the service provide gRPC or WebSocket delivery?
- No gRPC, WebSocket, or TCP delivery endpoint is stated in the product facts. The documented wire contract is raw UDP with no ordering, retransmission, or backpressure. Customers that require decoded records, server-side filtering, or a reliable stream need a separate processing layer or a different product category.