Skip to content

Whisper Agent Identity (Independent Publisher)#4225

Open
kakooch wants to merge 2 commits into
microsoft:devfrom
kakooch:whisper-agent-identity-independent-publisher
Open

Whisper Agent Identity (Independent Publisher)#4225
kakooch wants to merge 2 commits into
microsoft:devfrom
kakooch:whisper-agent-identity-independent-publisher

Conversation

@kakooch

@kakooch kakooch commented Jul 1, 2026

Copy link
Copy Markdown

Whisper Agent Identity (Independent Publisher)


When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected.

  • I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
  • I attest that the connector works and I verified by deploying and testing all the operations.
  • I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
  • I attest that I have added response schemas to my actions, unless the response schema is dynamic.
  • I validated the swagger file, apiDefinition.swagger.json. (Validated as OpenAPI 2.0 with openapi-spec-validator; paconn validate requires an interactive Power Platform sign-in.)
  • If this is an independent publisher connector, I confirm that I am not submitting a connector icon. (No icon is included; only iconBrandColor is set.)

Independent Publisher attestations:

  • I have named this PR after the pattern of "Connector Name (Independent Publisher)".
  • Within this PR I have pasted screenshots that show 3 unique operations working within a Flow, with each Flow succeeding. <-- add screenshots
  • Within this PR I have pasted a screenshot from the Test operations section within the Custom Connector UI. <-- add screenshot
  • If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md. (N/A — no OAuth. The only credential is an optional API key, documented in the readme.)

Whisper Agent Identity

Give every AI agent a real, routable IPv6 /128 identity (from 2a04:2a01::/32, announced by AS219419), anchored in DNS, RDAP and a tamper-evident transparency log — and operate it from Power Platform.

This is a two-tier connector (Postel's law):

  • Keyless (no key): verify an agent's identity by its IPv6 address, look up its RDAP record, read its transparency log, and see who has been resolving its name. Served from rdap.whisper.online.
  • Keyed (your Whisper API key): register agents, list your fleet, set per-tenant resolver policy, read activity logs, and revoke. Served from the Whisper control plane.

Single connection, both tiers

The API key is an optional connection parameter (api_key, securestring, required: false). It is injected as the X-API-Key header only on the five control operations (via a setheader policy), and those operations are routed to the control-plane host/path with dynamichosturl + routerequesttoendpoint. The four keyless operations stay on the default host and require no key. So:

  • Leave the key blank → keyless operations work; a control operation returns a clear 400 ("an attributable API key is required").
  • Provide the key → the full control plane unlocks; keyless operations keep working.

This is the same no-auth-plus-connection-parameter-plus-policy pattern used by existing connectors in this repo (e.g. ExchangeRate), so a single connector covers both tiers without a second auth policy.

Operations

Operation Tier Description
Verify agent identity keyless Full verification chain (PTR + FCrDNS AAAA + DANE-TLSA + signed identity doc) → one verdict.
RDAP lookup for an agent address keyless RDAP (RFC 9082/9083) record for a /128.
Get identity transparency log keyless Append-only, hash-chained, ES256-signed issuance/revocation log.
Get inbound identity lookups keyless Who resolved/queried the agent's name (k-anonymised source prefixes).
Register a new agent keyed Mint a new agent + its own /128 + its own API key (returned once).
List your agents keyed List your fleet, confined to your tenant.
Set resolver policy keyed Read/set per-tenant DNS policy (default allow/deny + block/allow lists).
Get activity logs keyed Recent DNS / connection / allocation activity.
Revoke an agent keyed Fully revoke an agent (withdraw /128, PTR, tokens, key).

Live checks (canonical example agent "scout", no key required)

$ curl -s "https://rdap.whisper.online/verify-identity?ip=2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478"
{ "is_whisper_agent": true, "fqdn": "...agents.whisper.online", "dane_ok": true, "jws_ok": true, ... }

$ curl -s "https://rdap.whisper.online/ip/2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478"              # RDAP
$ curl -s "https://rdap.whisper.online/ip/2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478/transparency"
$ curl -s "https://rdap.whisper.online/ip/2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478/lookups"

Control plane (needs your key, whisper_live_... — redacted here):

$ curl -s -X POST "https://graph.whisper.security/api/query" \
    -H 'content-type: application/json' -H 'X-API-Key: whisper_live_********' \
    -d '{"query":"CALL whisper.agents({op:'\''list'\'', args:{kind:'\''agents'\''}})"}'

An anonymous control call returns a clear problem object: "anonymous callers cannot use the agent control plane — an attributable API key is required" (HTTP 400).

Whisper Security added 2 commits July 1, 2026 15:49
Add the Whisper Agent Identity independent publisher connector: a public,
keyless connector to verify an AI agent's Whisper IPv6 /128 identity, look up
its RDAP record, read its tamper-evident identity transparency log, and see who
has been resolving its name. Anonymous authentication (no account or API key).
…ne (two-tier)

Rebuild the connector as two-tier per Postel's law. Keep the four public,
keyless identity operations (verify, RDAP, transparency, inbound lookups) on
rdap.whisper.online, and add five control operations (register, list, set
policy, logs, revoke) routed to the Whisper control plane.

The API key is an optional connection parameter (securestring, required:false).
It is injected as the X-API-Key header only on the control operations via a
setheader policy; those operations are sent to the control host/path with
dynamichosturl + routerequesttoendpoint. One connection covers both tiers: leave
the key blank and the keyless operations work; provide it and the control plane
unlocks. Same no-auth + connection-parameter + policy pattern already used in
this repo (e.g. ExchangeRate).

Swagger validated as OpenAPI 2.0.
@kakooch kakooch requested a review from a team as a code owner July 1, 2026 17:41
@microsoft-github-policy-service

Copy link
Copy Markdown
Contributor

@kakooch please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

  1. Definitions.
    “Code” means the computer software code, whether in human-readable or machine-executable form,
    that is delivered by You to Microsoft under this Agreement.
    “Project” means any of the projects owned or managed by Microsoft and offered under a license
    approved by the Open Source Initiative (www.opensource.org).
    “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
    Project, including but not limited to communication on electronic mailing lists, source code control
    systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
    discussing and improving that Project, but excluding communication that is conspicuously marked or
    otherwise designated in writing by You as “Not a Submission.”
    “Submission” means the Code and any other copyrightable material Submitted by You, including any
    associated comments and documentation.
  2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
    Project. This Agreement covers any and all Submissions that You, now or in the future (except as
    described in Section 4 below), Submit to any Project.
  3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
    Should You wish to Submit materials that are not Your original work, You may Submit them separately
    to the Project if You (a) retain all copyright and license information that was in the materials as You
    received them, (b) in the description accompanying Your Submission, include the phrase “Submission
    containing materials of a third party:” followed by the names of the third party and any licenses or other
    restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
    guidelines concerning Submissions.
  4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
    for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
    Submission is made in the course of Your work for an employer or Your employer has intellectual
    property rights in Your Submission by contract or applicable law, You must secure permission from Your
    employer to make the Submission before signing this Agreement. In that case, the term “You” in this
    Agreement will refer to You and the employer collectively. If You change employers in the future and
    desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
    and secure permission from the new employer before Submitting those Submissions.
  5. Licenses.
  • Copyright License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
    Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
    the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
    parties.
  • Patent License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
    Your patent claims that are necessarily infringed by the Submission or the combination of the
    Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
    import or otherwise dispose of the Submission alone or with the Project.
  • Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
    No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
    granted by implication, exhaustion, estoppel or otherwise.
  1. Representations and Warranties. You represent that You are legally entitled to grant the above
    licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
    have disclosed under Section 3). You represent that You have secured permission from Your employer to
    make the Submission in cases where Your Submission is made in the course of Your work for Your
    employer or Your employer has intellectual property rights in Your Submission by contract or applicable
    law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
    have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
    You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
    REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
    EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
    PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
    NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
  2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
    You later become aware that would make Your representations in this Agreement inaccurate in any
    respect.
  3. Information about Submissions. You agree that contributions to Projects and information about
    contributions may be maintained indefinitely and disclosed publicly, including Your name and other
    information that You submit with Your Submission.
  4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
    the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
    Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
    exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
    defenses of lack of personal jurisdiction and forum non-conveniens.
  5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

@vmanoharas

Copy link
Copy Markdown
Contributor

Hi @kakooch,

Thank you for your interest in submitting the IP connector. Please accept the CLA.

image

Additionally, Independent Publisher connector process has been changed.

Please refer below document and prepare connector package - https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission

Please refer this document for IP connector certification process - https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants