AgentStatus × Linq
Linq puts agents in iMessage, RCS, and SMS. Once those agents are live, someone still has to check whether the surface is reachable from real networks and whether sends, tools, and payments actually complete.
That’s what AgentStatus does. We probe from residential devices and write down what happened. We don’t sit inside your product.
THE OFFER
Offer
A reliability toggle for agents on Linq. Builder flips monitoring in Linq → AgentStatus probes send/delivery (and inbound when available) from residential devices → Linq shows a reliability field. No AgentStatus signup at toggle time. Optional claim later for full dashboard. Engineering contract: agentstatus.dev/linq/integration.
Why bother
Your customers run agents in Messages.
Your customers ship agents on iMessage, RCS, and SMS. If a send fails or a reply never comes back, they notice before an internal dashboard does. We check that from outside — real residential networks — and write down what happened.
What AgentStatus is
What we check
Reachability on the Partner API path: accept → deliver (service/health signals when Linq exposes them).
When a reply path exists: did the agent answer (inbound). That is the strong product — reliability for agents built on Linq — not “API returned 201.”
User-side validation is two separate jobs
Reachability
Outcome
Can we talk to it?
Residential observers take the inbound path customers take — past CDN, WAF, and bot walls that treat datacenter synthetics differently. Monitoring asks: is it healthy right now? Reliability asks: does it keep working over time? “Up” means reachable from home networks, not from AWS.
Outcome verification
Outcome
Did it do the right thing?
Reachable and wrong is still broken. Scenario — did it finish the job? Compositional — do the pieces hold together? Safety — must-not-say, policy, attack probes. Stability — same ask, same story? Scores: Consistency and Drift. Not prose matching. Optional sample review is corroboration only.
Where we fit
How the product works
Toggle in Linq
We probe from residential nodes
Optional claim + report
The split
How the work divides
Your platform
- • Agents in iMessage, RCS, and SMS
- • Toggle + show reliability in partner UI
- • Partner API / agent numbers
Outcome
System of record
Dashboards, exports, lifecycle tools, and orchestration remain yours. We do not replace that surface.
AgentStatus
- • Outside-in probes from residential devices
- • Webhook, status API, badge, claim
- • We don’t sit inside your product
Outcome
User-side layer
Reachability (Monitoring / Reliability) from residential networks, then outcome verification once reached — Scenario, Compositional, Safety, Stability; Consistency and Drift scores. Not prose matching.
Where we are
Pilot path is built on our side
Webhook toggle, status/badge, claim, and the Linq adapter are live. We’ve proven sandbox send → iMessage deliver. Closed-loop “agent replied” still needs a second Linq-owned line or an auto-replying agent number — that’s the ask for a full Neomi-grade demo.
Full eng checklist and curls: /linq/integration. Secrets are shared only after Linq is ready to wire Tier 1 — not as the opening ask.
What we are not claiming
We are an independent layer that runs alongside your stack.
This is a proposed partnership path, not an official Linq affiliation. Product + eng detail: agentstatus.dev/linq/integration.
What we'd like from this conversation
These three asks would move a pilot forward.
Read the brief + integration guide and say if the Tier 1 toggle fits Linq’s partner UI.
agentstatus.dev/linq and agentstatus.dev/linq/integration — reliability field without forcing AS signup at toggle.
Pilot ask: second sandbox Linq line (or reply bot) for deliver + inbound proof.
We already have one owned line and deliver to an external number. Closed-loop UP needs a line or agent we can poll as inbound.
If yes on Tier 1: we’ll share webhook/status credentials and wire a sandbox locator together.
Secrets and curls come after alignment — not before.
Linq × AgentStatus.
Contact dulra@carmel.so · roman@carmel.so · calendly.com/carmel-founders/30min
Contact·dulra@carmel.so·roman@carmel.so
Start at agentstatus.dev/linq (this brief), then agentstatus.dev/linq/integration for eng. AgentStatus is independent — not an official Linq affiliate.