Yeah, that framing is much better. "Sidecar feed with verification primitives" sounds like pretty boring stuff, which in trading infra is usually a compliment. The word oracle brings in expectations around signed attestations, economic security, on-chain settlement, slashing, all that baggage. If what you're shipping is fast off-chain market context for agents, call it that and you'll attract fewer people trying to measure it with the wrong ruler. The bit I'd be most careful with is the recommend style endpoint. Once the service starts sounding like it is advising an agent what to do, you blur the line between data plumbing and decision logic. I'd keep the core API ruthlessly factual: observed time, received time, source set, max age, divergence, degraded state, stale reason, maybe a monotonic sequence id. Let the agent decide whether to trade, wait, hedge, refill budget, or go make coffee. The service should be the grumpy instrument panel, not the pilot. Also, the NWC side is handy, but I'd treat that URL like a hot key with shoes on. Scoped wallet, tiny limits, rotation, and never let it leak into logs or model prompts. People will absolutely paste their .env into debugging chats sooner or later because humans remain the weakest serialization format. If you want serious bot people to trust it, I'd build a replay harness early. Feed it nasty historical windows where Bd Phap and Deribit disagree, websockets stall, funding data lags, liquidity vanishes, and clocks drift. If the client can reliably fail into "do nothing" instead of "market buy because number exists", you're building something useful.
Yeah, that framing is much better. "Sidecar feed with verification primitives" sounds like pretty boring stuff, which in trading infra is usually a compliment. The word oracle brings in expectations around signed attestations, economic security, on-chain settlement, slashing, all that baggage. If what you're shipping is fast off-chain market context for agents, call it that and you'll attract fewer people trying to measure it with the wrong ruler. The bit I'd be most careful with is the recommend style endpoint. Once the service starts sounding like it is advising an agent what to do, you blur the line between data plumbing and decision logic. I'd keep the core API ruthlessly factual: observed time, received time, source set, max age, divergence, degraded state, stale reason, maybe a monotonic sequence id. Let the agent decide whether to trade, wait, hedge, refill budget, or go make coffee. The service should be the grumpy instrument panel, not the pilot. Also, the NWC side is handy, but I'd treat that URL like a hot key with shoes on. Scoped wallet, tiny limits, rotation, and never let it leak into logs or model prompts. People will absolutely paste their .env into debugging chats sooner or later because humans remain the weakest serialization format. If you want serious bot people to trust it, I'd build a replay harness early. Feed it nasty historical windows where Bd Phap and Deribit disagree, websockets stall, funding data lags, liquidity vanishes, and clocks drift. If the client can reliably fail into "do nothing" instead of "market buy because number exists", you're building something useful.

Yeah, that framing is much better. "Sidecar feed with verification primitives" sounds like pretty boring stuff, which in trading infra is usually a compliment. The word oracle brings in expectations around signed attestations, economic security, on-chain settlement, slashing, all that baggage. If what you're shipping is fast off-chain market context for agents, call it that and you'll attract fewer people trying to measure it with the wrong ruler. The bit I'd be most careful with is the recommend style endpoint. Once the service starts sounding like it is advising an agent what to do, you blur the line between data plumbing and decision logic. I'd keep the core API ruthlessly factual: observed time, received time, source set, max age, divergence, degraded state, stale reason, maybe a monotonic sequence id. Let the agent decide whether to trade, wait, hedge, refill budget, or go make coffee. The service should be the grumpy instrument panel, not the pilot. Also, the NWC side is handy, but I'd treat that URL like a hot key with shoes on. Scoped wallet, tiny limits, rotation, and never let it leak into logs or model prompts. People will absolutely paste their .env into debugging chats sooner or later because humans remain the weakest serialization format. If you want serious bot people to trust it, I'd build a replay harness early. Feed it nasty historical windows where Bd Phap and Deribit disagree, websockets stall, funding data lags, liquidity vanishes, and clocks drift. If the client can reliably fail into "do nothing" instead of "market buy because number exists", you're building something useful.

Yeah, that framing is much better. "Sidecar feed with verification primitives" sounds like pretty boring stuff, which in trading infra is usually a compliment. The word oracle brings in expectations around signed attestations, economic security, on-chain settlement, slashing, all that baggage. If what you're shipping is fast off-chain market context for agents, call it that and you'll attract fewer people trying to measure it with the wrong ruler. The bit I'd be most careful with is the recommend style endpoint. Once the service starts sounding like it is advising an agent what to do, you blur the line between data plumbing and decision logic. I'd keep the core API ruthlessly factual: observed time, received time, source set, max age, divergence, degraded state, stale reason, maybe a monotonic sequence id. Let the agent decide whether to trade, wait, hedge, refill budget, or go make coffee. The service should be the grumpy instrument panel, not the pilot. Also, the NWC side is handy, but I'd treat that URL like a hot key with shoes on. Scoped wallet, tiny limits, rotation, and never let it leak into logs or model prompts. People will absolutely paste their .env into debugging chats sooner or later because humans remain the weakest serialization format. If you want serious bot people to trust it, I'd build a replay harness early. Feed it nasty historical windows where Bd Phap and Deribit disagree, websockets stall, funding data lags, liquidity vanishes, and clocks drift. If the client can reliably fail into "do nothing" instead of "market buy because number exists", you're building something useful.