A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: "Siemens Runs Its Own A2A Agent. What I Found At Schneider Electric And Rockwell Automation.," Kin Lane, November 12, 2026, https://apievangelist.com/2026/11/12/siemens-runs-its-own-a2a-agent-what-i-found-at-schneider-electric-and-rockwell-automation/
Priya was a sourcing analyst at a firm that builds packaging lines, and she spent most of her mornings hunting for datasheets. She read Kin Lane's post on a Thursday between two supplier calls. The headline named Siemens, and she had a Siemens part number open in another tab.
The post said Siemens runs a dedicated host for its agent, and that one of its five live skills hands back a product's datasheet when you give it an article number. The post describes the skill this way: "Returns the technical datasheet for one Siemens industry product by its article number, as structured data." She sat back. Last month she had copied values out of PDFs into a spreadsheet by hand. A lookup by article number that returned structured data was the job she actually did.
Then she got suspicious, which was her habit. A card existing isn't the same as the thing working for the parts she bought. The author had been straightforward about that. On the MCP endpoint he only confirmed that a plain GET returns a 405 and a JSON body, and he wrote that he did not go further. She respected that. It also meant she still didn't know whether the datasheet skill returned good values for her parts.
The other two companies bothered her more. The post says three hosts were probed for each of Schneider Electric and Rockwell Automation, and no agent card turned up. On the developer hosts, one did not answer and one did not resolve. Two of her three biggest suppliers sat in that gap. She felt a small irritation, the kind you get when a tidy comparison table makes your own situation look like a deficiency. A table cell reading "No (3 hosts checked)" was no reason to switch vendors, and she said so aloud to nobody.
Still, one line stayed with her: "That is the kind of sentence that saves an integrator an afternoon." She had lost plenty of afternoons. Near the end the post says, "Start with public data." She thought about her own company's public data, which was thin and mostly PDF. Nobody there had ever imagined an agent wanting it.
She didn't write a proposal. She opened a terminal and requested the two well-known paths on her company's main domain. Both came back 404, as she had expected. Then she opened a blank note and typed one plain sentence describing what a datasheet lookup by article number would return for their flagship line. Under it she added the post's advice about describing each skill so another agent knows what it is getting. She saved the note in the shared folder for the web team and left it there for Monday.