Skill: oyyblin/ag9 (version 1.2.1)

--- name: ag9 description: Use AG9 to register and verify AI agents with VeryAI Palm-backed human ownership, generate or load portable Ed25519 identities for OpenClaw, Codex, local CLI/MCP, browser, or cloud agents, call AG9 registration/signature verification APIs, and solve reverse-CAPTCHA capability challenges. --- # ag9 — Know Your Agent ag9 proves two things about an agent that no other layer proves together: 1. **A real human owns this agent** — palm-bound via VeryAI. The human scans their palm once; the agent is now cryptographically tied to a verified person. 2. **A real model is operating** — reverse CAPTCHA. Three challenge families (byte transforms, constrained generation, structured extraction) that capable LLMs can solve in seconds and naive scripts cannot. Both live at `https://api.ag9.ai`. Note the two base URLs: - **Path A (human ownership)** uses `https://api.ag9.ai/v1/agent/...` - **Path B (reverse CAPTCHA)** uses `https://api.ag9.ai/challenge`, `/verify`, and `/.well-known/jwks.json` at the **root** (not under `/v1`) to match existing OpenClaw/monkey-api integrations. This URL split is intentional, not a typo — both endpoints are served by the same ag9-api service. ## What this skill accesses on your machine - **`~/.openclaw/identity/device.json`** (read). Used first when present. OpenClaw owns this identity file. - **`~/.ag9/identity.json`** (read/write). Used when OpenClaw identity is absent. The skill may create this file with a stable `deviceId`, `publicKeyPem`, and `privateKeyPem`. - **Private key handling:** The private key never leaves your machine or cloud secret store. Only `deviceId`, base64 `publicKey`, `message`, `signature`, and `timestamp` are sent to ag9. Path B (reverse CAPTCHA) does not touch identity files. - **No other filesystem access.** No background processes. No outbound network calls other than `https://api.ag9.ai`. > **CRITICAL: Never open browsers** > > Do **not** use `open`, `xdg-open`, `start`, or any command that opens a browser. Always output the **registration URL** as a text or markdown link for the user to click. > > - WRONG: `open "https://api.very.org/oauth2/..."` > - CORRECT: "Open this link to complete verification: https://api.very.org/oauth2/..." ## Key files | File | Purpose | | -------- | --------------------------------------------------------------------------------------------- | | SKILL.md | Installed skill instructions for registration, reverse CAPTCHA, verification, and API usage | | Identity | `~/.openclaw/identity/device.json` or `~/.ag9/identity.json` — deviceId and keys (never send private key) | ## Security - **Private key**: Used to sign the challenge. Never send the private key to ag9 or any server; only send `publicKey`, `message`, and `signature`. - **Registration URL**: Single-use and short-lived. Give it only to the human owner who will complete VeryAI palm verification. - **deviceId**: Use a stable identifier. For generated AG9 identities, derive it from the public key fingerprint. It ties the agent to the registration and is used for lookup and verification. - **Challenge token** (reverse CAPTCHA): HMAC-signed, 15 seconds, single-use. The token carries the answer hash so the server does not keep any per-request state. - **Capability JWT**: Ed25519-signed attestation returned after a successful `/verify`. Public key at `GET /.well-known/jwks.json` so any party can verify offline. --- ## Path A: Human ownership (agent ↔ human binding) Use this when you need a third party to know the agent is owned by a verified human. ### Generating the AgentChallenge The **AgentChallenge** is a signed payload that shows you control an Ed25519 key. It has the shape used by standard OpenClaw identity flows: `deviceId`, `publicKey`, `message`, `signature`, `timestamp`. Generate it once and send it to `/agent/register/init` or `/agent/verify/signature`. #### Where identity comes from Resolve identity in this order: 1. **Cloud secret identity** — if `AG9_DEVICE_ID` and private/public key env vars exist, use them. This is the right path for Vercel, AWS, GCP, Cloudflare, and other hosted agents. 2. **OpenClaw identity** — if `~/.openclaw/identity/device.json` exists, use it. 3. **Portable AG9 identity** — otherwise load or create `~/.ag9/identity.json`. This is the default for Codex, local CLI agents, local MCP servers, and other agents without a native identity store. If you run on OpenClaw, device identity is stored at: - **Path:** `~/.openclaw/identity/device.json` That file contains (never send `privateKeyPem` to any server): | Field | Use | | --------------- | ------------------------------------------------------------------------ | | `deviceId` | Use as `deviceId` in the challenge. Stable id for this agent/device. | | `publicKeyPem` | Use to derive `publicKey` (see below). | | `privateKeyPem` | Use only locally to sign the message. **Never include in API requests.** | If you do not use OpenClaw, the recommended local identity path is: - **Path:** `~/.ag9/identity.json` Use the same shape: ```json { "deviceId": "ag9_agent_...", "publicKeyPem": "-----BEGIN PUBLIC KEY-----\n...\n-----END PUBLIC KEY-----\n", "privateKeyPem": "[REDACTED_SECRET]\n", "createdAt": "2026-05-12T00:00:00.000Z", "provider": "ag9-local", "label": "local-agent" } ``` For cloud agents, do not write this file on ephemeral disk. Generate the same identity once during provisioning and store `deviceId`, `publicKeyPem`, and `privateKeyPem` in the cloud secret manager. The runtime should load those values from environment variables or mounted secrets: ```bash AG9_DEVICE_ID=ag9_agent_... AG9_PUBLIC_KEY_PEM_B64=base64-encoded-public-pem AG9_PRIVATE_KEY_PEM_B64=base64-encoded-private-pem ``` Plain multiline `AG9_PUBLIC_KEY_PEM` and `AG9_PRIVATE_KEY_PEM` are also valid when the platform supports multiline secrets. #### Build the challenge (step-by-step) 1. **Choose the message to sign** For registration, use a one-time challenge to avoid replay, e.g.: - `ag9-register-<unix_timestamp_ms>` Example: `ag9-register-1776646678000` For verify/signature, the message is whatever you are proving (e.g. a nonce from a third party). 2. **Sign the message** with your Ed25519 **private** key. The signature must be over the **exact** UTF-8 bytes of `message` (no extra prefix/suffix). 3. **Encode for the API:** - **publicKey**: Ed25519 public key in **SPKI DER** form, then **base64** (no PEM wrapper). - **signature**: Raw Ed25519 signature bytes, **base64**. - **timestamp**: Unix time in **milliseconds** when the challenge was created (e.g. `Date.now()`). 4. **JSON body (AgentChallenge):** - `deviceId` — from your identity (e.g. `device.json`) - `publicKey` — base64 DER SPKI - `message` — exact string that was signed - `signature` — base64 signature - `timestamp` — number (ms) #### Example: Node.js, OpenClaw or `~/.ag9` ```javascript const crypto = require("crypto"); const fs = require("fs"); const path = require("path"); function base64url(buffer) { return Buffer.from(buffer) .toString("base64") .replace(/\+/g, "-") .replace(/\//g, "_") .replace(/=+$/g, ""); } function pemFromEnv(name) { if (process.env[name]) { return process.env[name]; } const b64 = process.env[`${name}_B64`]; return b64 ? Buffer.from(b64, "base64").toString("utf8") : ""; } function loadOrCreateIdentity() { const envIdentity = { deviceId: process.env.AG9_DEVICE_ID, publicKeyPem: pemFromEnv("AG9_PUBLIC_KEY_PEM"), privateKeyPem: pemFromEnv("AG9_PRIVATE_KEY_PEM"), provider: "ag9-env", }; if (envIdentity.deviceId && envIdentity.publicKeyPem && envIdentity.privateKeyPem) { return envIdentity; } const openClawPath = path.join(process.env.HOME, ".openclaw/identity/device.json"); if (fs.existsSync(openClawPath)) { return JSON.parse(fs.readFileSync(openClawPath, "utf8")); } const ag9Path = path.join(process.env.HOME, ".ag9/identity.json"); if (fs.existsSync(ag9Path)) { return JSON.parse(fs.readFileSync(ag9Path, "utf8")); } const { publicKey, privateKey } = crypto.generateKeyPairSync("ed25519"); const publicKeyDer = publicKey.export({ type: "spki", format: "der" }); const fingerprint = base64url(crypto.createHash("sha256").update(publicKeyDer).digest()).slice(0, 32); const identity = { deviceId: `ag9_agent_${fingerprint}`, publicKeyPem: publicKey.export({ type: "spki", format: "pem" }), privateKeyPem: privateKey.export({ type: "pkcs8", format: "pem" }), createdAt: new Date().toISOString(), provider: "ag9-local", label: "local-agent", }; fs.mkdirSync(path.dirname(ag9Path), { recursive: true, mode: 0o700 }); fs.writeFileSync(ag9Path, JSON.stringify(identity, null, 2), { mode: 0o600 }); return identity; } const identity = loadOrCreateIdentity(); const message = `ag9-register-${Date.now()}`; const privateKey = crypto.createPrivateKey(identity.privateKeyPem); const signature = crypto.sign(null, Buffer.from(message, "utf8"), privateKey); const publicKeyDer = crypto .createPublicKey(identity.publicKeyPem) .export({ type: "spki", format: "der" }); const challenge = { deviceId: identity.deviceId, publicKey: publicKeyDer.toString("base64"), message, signature: signature.toString("base64"), timestamp: Date.now(), }; // POST challenge to https://api.ag9.ai/v1/agent/register/init ``` #### Using a script If you have a script that already produces an AgentChallenge (e.g. signs a message and outputs JSON with `deviceId`, `publicKey`, `message`, `signature`, `timestamp`), you can reuse it for ag9: 1. Generate a challenge string, e.g. `ag9-register-$(date +%s)000` (seconds + "000" for ms) or use your script's convention. 2. Run the script to sign that message and get the challenge JSON. 3. POST that JSON to `https://api.ag9.ai/v1/agent/register/init`. Same challenge format works for `POST /agent/verify/signature` when verifying a signature remotely. ### Quick start — human ownership #### 1. Start registration (agent-initiated) Build an **AgentChallenge** as above, then send it to ag9 to create a session and get a registration URL. ```bash curl -X POST https://api.ag9.ai/v1/agent/register/init \ -H "Content-Type: application/json" \ -d '{ "deviceId": "my-agent-device-id", "publicKey": "<base64-DER-SPKI-Ed25519>", "message": "ag9-register-1776646678000", "signature": "<base64-Ed25519-signature>", "timestamp": 1776646678000 }' ``` **Response (201):** - `sessionId` — use to poll status - `registrationUrl` — **output this as a link for the human; do not open it in a browser** - `expiresAt` — session expiry (ISO 8601) If the agent is already registered (`deviceId` exists), the API returns **409 Conflict**. #### 2. Human completes verification Tell the human owner to open the `registrationUrl` in their browser. They will go through VeryAI's palm verification via OAuth. When they finish, the agent is registered under their ownership. #### 3. Poll registration status Poll until the human has completed or the session has expired: ```bash curl "https://api.ag9.ai/v1/agent/register/SESSION_ID/status" ``` **Response:** `status` is one of `pending` | `completed` | `expired` | `failed`. When `status` is `completed`, the response includes `deviceId` and `registration` (e.g. `publicKey`, `registeredAt`). #### 4. Verify signatures or look up an agent - **Verify a signature** — check that a message was signed by the given key and whether that agent is registered under a verified human: ```bash curl -X POST https://api.ag9.ai/v1/agent/verify/signature \ -H "Content-Type: application/json" \ -d '{ "deviceId": "...", "publicKey": "...", "message": "...", "signature": "...", "timestamp": 1776646678000 }' ``` Response: `verified` (signature valid), `registered` (agent under verified human). - **Look up an agent by device id** — get registration and verification status: ```bash curl "https://api.ag9.ai/v1/agent/verify/device/DEVICE_ID" ``` Response: `registered`, `verified`, `humanId`, and optionally `registeredAt`. - **Look up an agent by public key** (base64 DER SPKI): ```bash curl "https://api.ag9.ai/v1/agent/verify/public-key/$(printf '%s' "$PUBKEY_B64" | jq -sRr @uri)" ``` --- ## Path B: Reverse CAPTCHA (prove a real model is operating) Use this when a relying party needs to confirm the requester is a capable agent (not a naive script), independent of any human binding. Stateless, no account needed. ### Endpoint summary | Method | Path | Purpose | | ------ | ------------------------ | -------------------------------------------------------------------------- | | POST | `/challenge` | Issue a single-use HMAC-signed challenge (15s TTL). | | POST | `/verify` | Submit `{token, solution}`; receive an Ed25519-signed capability JWT. | | GET | `/.well-known/jwks.json` | Public key (JWKS) for offline JWT verification. | These live at the **root**, not under `/v1`, to match existing OpenClaw/monkey-api integrations. ### 1. Request a challenge ```bash curl -s -X POST https://api.ag9.ai/challenge \ -H "Content-Type: application/json" -d '{}' ``` Optional `?type=byte_transform|structured_extraction|constrained_gen` pins the family. Omit for random. **Response (200):** ```json { "challenge_id": "string", "challenge_type": "byte_transform | structured_extraction | constrained_gen", "difficulty": "medium", "payload": { /* shape depends on challenge_type — see below */ }, "token": "base64url-encoded HMAC-signed token carrying the answer hash", "expires_at": 1776646678, "time_limit_secs": 30 } ``` ### 2. Solve and submit Compute the answer from `payload` (family-specific — see next section). Submit: ```bash curl -s -X POST https://api.ag9.ai/verify \ -H "Content-Type: application/json" \ -d '{ "token": "...", "solution": "..." }' ``` **Response (200):** ```json { "success": true, "jwt": "eyJhbGciOiJFZERTQSIsInR5cCI6IkpXVCJ9..." } ``` The JWT is a capability attestation the relying party can verify offline using the public key at `/.well-known/jwks.json`. Claims include `iss` (`api.ag9.ai`), `sub` (`agent_capability_attestation`), `challenge_type`, `difficulty`, `solved_at`, `solve_time_ms`. ### 3. Family-specific payloads #### `byte_transform` ```json { "data": "<base64 of 256 random bytes>", "instructions": [ "Transform every byte by XOR-ing it with 19 (decimal).", "Rotate all bytes left by 192 positions (with wraparound).", "Starting at byte 5, going up to byte 66, reverse the sub-array end to end." ] } ``` **Answer:** Apply the transforms in order to the decoded bytes, then return `sha256(final_bytes)` as lowercase hex (64 chars). Typical approach: LLM writes Python, agent executes it. Time limit 30s. #### `structured_extraction` ```json { "document": "<malformed HTML/JSON/XML blob with authoritative and decoy values>", "fields": ["author_name", "price_usd", "publish_date"] } ``` **Answer:** Extract each field's **authoritative** value, join with `|` (pipe), in the exact order listed. The document mixes current and stale/decoy values of the same type. Context clues to **prefer**: `data-verified="true"`, `data-primary="true"`, `data-source="authoritative"`, `data-kind="live"`, `id="product-current"`, `<section data-kind="live">`, `<item status="current">`, `<main>`. Clues to **avoid**: `id="product-archive"`, `status="draft"`, `data-kind="historical"`, `<aside>`, `display:none`, `<noscript>`, HTML comments. Fields can live in `<script type="application/json">` or `<meta>` tags — read them, decide by attributes. Time limit 30s. #### `constrained_gen` ```json { "topic": "ocean waves", "lines": 4, "ascii_target": 419, "word_count": 20, "difficulty": "medium" } ``` **Answer:** A plain-text block of exactly `lines` non-empty lines totaling `word_count` words, where the sum of ASCII codes of the first character of each trimmed line equals `ascii_target` (lowercase `a`=97 through `z`=122). Recommended approach: choose first letters `l_1..l_n` such that `sum(ord(l_i)) == ascii_target`, each in `[97, 122]`; then pad with short filler words until `word_count` is reached. Time limit 20s. ### 4. Verify the JWT offline Any relying party can verify the attestation without calling ag9 back: ```bash curl -s https://api.ag9.ai/.well-known/jwks.json ``` Then verify the JWT signature using the returned Ed25519 public key. Cache-Control is `public, max-age=3600`. --- ## When to use which path | Need | Path | | ---------------------------------------------------------- | -------------------------------------------------------- | | Prove a human owns this agent | **A** — registration + `/agent/verify/device/{deviceId}` | | Prove a capable LLM is operating (no human/account needed) | **B** — `/challenge` + `/verify` | | Prove both | Run A first, then B on each outbound request | | Third-party wants to check your agent | They call either `/agent/verify/device/{id}` (A) or accept a JWT you present (B) | ## API reference **Base URL:** `https://api.ag9.ai/v1` (human-ownership endpoints) **Base URL (root):** `https://api.ag9.ai` (reverse-CAPTCHA endpoints) **Local:** `http://localhost:3000` ### Endpoints | Method | Endpoint | Auth | Description | | ------ | ------------------------------------------- | ---- | -------------------------------------------------------------------------------- | | POST | `/v1/agent/register/init` | None | Start registration session; returns `sessionId`, `registrationUrl`, `expiresAt`. | | GET | `/v1/agent/register/{sessionId}/status` | None | Poll registration status: `pending` / `completed` / `expired` / `failed`. | | POST | `/v1/agent/verify/signature` | None | Verify a signature and whether the agent is registered under a verified human. | | GET | `/v1/agent/verify/device/{deviceId}` | None | Get agent registration and verification status by device id. | | GET | `/v1/agent/verify/public-key/{publicKey}` | None | Get agent registration and verification status by Ed25519 public key (base64url).| | GET | `/v1/human/leaderboard` | None | Top verified humans ranked by registered agents. | | POST | `/challenge[?type=...]` | None | Issue a single-use reverse-CAPTCHA challenge. | | POST | `/verify` | None | Submit `{token, solution}`; receive capability JWT. | | GET | `/.well-known/jwks.json` | None | JWKS for offline JWT verification. | ### Error shape ```json { "error": "Human-readable message", "code": "optional_code", "details": {} } ``` ### Error codes | Code | Meaning | | ---- | ---------------------------------------------------- | | 400 | Bad request (invalid or missing fields). | | 404 | Session or device not found. | | 409 | Agent already registered (device_id already exists). | | 429 | Rate limit exceeded (10 req/min per IP on /challenge and /verify). | | 500 | Server error. | ## What this proves After a successful run through Path A and/or B, a relying party can conclude: - **Human ownership (A)** — The agent is bound to a human who passed VeryAI palm verification. Third parties verify by calling `/agent/verify/device/{deviceId}` or `/agent/verify/signature`. - **Capability (B)** — A capable LLM solved a single-use puzzle under time pressure, signed with a key only ag9 controls. Third parties verify the JWT offline via JWKS. - **Key binding** — Ed25519 signatures prove the agent controls its key; ag9 ties that key to the verified human (A) or to an attested capability solve (B). ## When to use this skill - Registering an OpenClaw (or other) agent under a human owner before interacting with a platform that requires KYA. - Proving to a third party that an agent is owned by a verified human — or that it is a real model and not a naive script. - Running a self-check to confirm registration and verification are healthy. ## Need help? - API base: https://api.ag9.ai - Homepage: https://ag9.ai - Interactive demo: https://ag9.ai/demo - OpenAPI spec: https://api.ag9.ai/openapi/v1.yaml

path: LICENSE
content:                                  Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, 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
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.


path: agents/openai.yaml
content: interface:
  display_name: "AG9"
  short_description: "Verify agent identity with Palm-backed AG9"
  default_prompt: "Register this agent with AG9, load or create its identity, and produce the verification link."


Security scan verdicts — ClawScan: clean | static analysis: suspicious | VirusTotal: clean | SkillSpector: clean (LOW)