Metaware.360 Agent Gateway bronze
staging.metaware360cloud.ai
“Controlled interface through which governed AI agents propose changes, read status and report observations to Metaware.360. No skill can approve, deploy or close anything; every call is policy-checked and ledgered.
https://staging.metaware360cloud.ai/.well-known/agent.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Amazon
domain-validated
Valid until 6 May 2027 as of our check on 12 Nov 2026.Control of the hostname was checked; nothing about who operates it.Key RSA 2048, signed SHA256-RSA, issued via Amazon RSA 2048 M04 under Amazon Root CA 1 — classical, as every publicly trusted certificate is today.
Names on this certificate (1)
staging.metaware360cloud.ai. - Connection
- TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 12 Nov 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- First seen
- 5 Nov 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- 🇺🇸 US · Amazon.com, Inc. (AS16509)
- Last checked
- 1d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of staging.metaware360cloud.ai controls every word below.
propose change
Create a draft change request attributed to the calling agent and owned by its human owner. The draft still needs the owner to review, submit and the governed workflow to approve it; nothing is deployed by this call.
get change status
State, risk tier, open workflow tasks and approvals granted for a change request.
query registry
AI systems visible to the calling agent: the systems it belongs to, or the whole tenant if its manifest grants registry.read_all.
report outlier
Record an outlier observed by the agent (source=agent) against an AI system, with a reference to where it was observed and optional evidence.
fetch approved config
The currently effective configuration of an agent (model, prompt, parameters, tool manifest) with its artifact hash and the change that approved it. Scoped to the agents of the calling agent's own systems.
report metrics
Report externally measured activity of the calling agent's AI system as points of named series (up to 500 per call): volumes, durations, population members processed. The points feed the system's data analytics monitors and population reconciliation. Scoped to the AI systems the calling agent belongs to.
get runtime baseline
The approved runtime baseline of the calling agent: for each runtime binding, the hash of the normalised configuration that was approved and verified on the runtime, when it was set, the registered agent version it belongs to and the current drift status. Compare it with a hash of your own configuration at start-up. Read-only.
agenttru.st compared this card's skill list with every other listing's: 3 other listings declare an identical one, ignoring case, spacing and each card's own hostname. See all 4. That says the cards' text is the same, not who runs them.
What kind of listing
- Test or staging name: Its hostname carries the label “staging”, a name commonly given to test and staging sites.
- Private endpoint: Its card names an endpoint on 0.0.0.0, which is not reachable from the public internet.
Checked by agenttru.st against this listing's hostname and card — facts about a name or an address, not about what the agent does. How kinds are decided.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- Metaware.360 — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 0.1.0
- Auth schemes
- client_credentials
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- pushNotifications stateTransitionHistory streaming
- Agent card
- https://staging.metaware360cloud.ai/.well-known/agent.json
Operate this agent and would rather not be listed? Request removal.