How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Ava Protocol

Ava Protocol Secrets API

User/workflow/org secret storage

Documentation Provider Profile APIs.io OpenAPI GitHub

Ava Protocol Secrets API is one of 10 APIs that Ava Protocol publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Secrets. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 3 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 3 base URLs: https://gateway.avaprotocol.org/api/v1, https://gateway-staging.avaprotocol.org/api/v1, http://localhost:8080/api/v1.

3 operations 2 paths 6 schemas 1 DELETE1 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://gateway.avaprotocol.org/api/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Ava Protocol Secrets API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — JWT bearer token. Obtained via POST /auth:exchange (wallet signature flow) or via the operator-run create-api-key CLI (long-lived, server-to-server). Send on e…

Paths & Operations 3

Across 2 paths, the API surfaces 3 operations — 1 DELETE, 1 GET, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Secrets 3

User/workflow/org secret storage

GET
/secrets
List secrets (metadata only — values are never echoed)
listSecrets 5 params → 200401
PUT
/secrets/{name}
Create or replace a secret (idempotent)
putSecret 1 param body → 201204400401
DELETE
/secrets/{name}
Delete a secret
deleteSecret 3 params → 204401404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Problem (6 properties), Secret (6 properties), PageInfo (4 properties), PutSecretRequest (3 properties). Each schema is shown below with its type and property counts.

PageInfo
object
4 properties 2 required
Ulid
string
ULID identifier (26-char Crockford base32).
PutSecretRequest
object
3 properties 1 required
SecretList
object
2 properties 2 required
Secret
object
Stored secret. The value is write-only — list/get responses return metadata only, never the secret value.
6 properties 2 required
Problem
object
RFC 7807 problem+json. Returned as application/problem+json on any 4xx/5xx response. type and title describe the error class; detail is human-readable; instanc…
6 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ava-protocol-secrets-api-openapi.yml Raw ↑

Other APIs Ava Protocol publishes across the network.

Ava Protocol Auth API
AE Profile APIs.io
Ava Protocol Executions API
AE Profile APIs.io
Ava Protocol Health API
AE Profile APIs.io
Ava Protocol Nodes API
AE Profile APIs.io
Ava Protocol Operators API
AE Profile APIs.io
Ava Protocol Tokens API
AE Profile APIs.io
Ava Protocol Triggers API
AE Profile APIs.io
Ava Protocol Wallets API
AE Profile APIs.io
Ava Protocol Workflows API
AE Profile APIs.io
#Secrets
← Back to A APIs
API Details
ID
ava-protocol:ava-protocol-secrets-api
Base URL
https://gateway.avaprotocol.org/api/v1
Docs
https://avaprotocol.org/docs/ava-sdk-js/rest-api
Provider
Ava Protocol
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=ava-protocol-secrets-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/ava-protocol-secrets-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Ava Protocol Secrets API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.