Safe (Gnosis Safe)
Safe (formerly Gnosis Safe) provides multi-signature smart contract wallets for managing digital assets on EVM-compatible blockchains. The Safe Transaction Service is a REST API that tracks transactions submitted to Safe smart contracts, enabling off-chain collection of signatures, owner notification of pending transactions, delegate management, on-chain message signing, and token/NFT balance retrieval across 40+ supported networks including Mainnet, Arbitrum, Optimism, Polygon, Base, Gnosis Chain, zkSync, and testnets. The Safe{Core} SDK (API Kit) provides a TypeScript client for the Transaction Service. Authentication uses JWT API keys with tiered plans ranging from a free Builder tier to high-throughput Scale plans.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Safe (Gnosis Safe) the way a machine reads it — 150 machine-readable artifacts across 16 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Safe (Gnosis Safe) scores 49.2/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Safe (Gnosis Safe)
Each block below is one kind of artifact we hold for Safe (Gnosis Safe). For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 16
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Safe Delegates API
Endpoints for managing delegate relationships on a Safe. Delegates are addresses authorized by Safe owners to propose transactions without being full owners. Supports creating, ...
Safe Messages API
Endpoints for off-chain message signing via Safe smart accounts. Allows creating signed messages for a Safe, retrieving existing messages by their hash, and listing all messages...
Safe 4337 User Operations API
Endpoints supporting ERC-4337 account abstraction user operations for Safe smart accounts. Allows listing, retrieving, and managing ERC-4337 user operations associated with a Sa...
Safe API Kit (TypeScript SDK)
Official TypeScript client SDK for the Safe Transaction Service API. Wraps all Transaction Service endpoints with typed methods for proposing transactions, confirming signatures...
Safe (Gnosis Safe) 4337 API
The 4337 API from Safe (Gnosis Safe) — 5 operation(s) for 4337.
Safe (Gnosis Safe) about API
The about API from Safe (Gnosis Safe) — 6 operation(s) for about.
Safe (Gnosis Safe) analytics API
The analytics API from Safe (Gnosis Safe) — 1 operation(s) for analytics.
Safe (Gnosis Safe) contracts API
The contracts API from Safe (Gnosis Safe) — 2 operation(s) for contracts.
Safe (Gnosis Safe) data-decoder API
The data-decoder API from Safe (Gnosis Safe) — 1 operation(s) for data-decoder.
Safe (Gnosis Safe) delegates API
The delegates API from Safe (Gnosis Safe) — 5 operation(s) for delegates.
Safe (Gnosis Safe) messages API
The messages API from Safe (Gnosis Safe) — 3 operation(s) for messages.
Safe (Gnosis Safe) modules API
The modules API from Safe (Gnosis Safe) — 2 operation(s) for modules.
Safe (Gnosis Safe) owners API
The owners API from Safe (Gnosis Safe) — 2 operation(s) for owners.
Safe (Gnosis Safe) safes API
The safes API from Safe (Gnosis Safe) — 6 operation(s) for safes.
Safe (Gnosis Safe) tokens API
The tokens API from Safe (Gnosis Safe) — 3 operation(s) for tokens.
Safe (Gnosis Safe) transactions API
The transactions API from Safe (Gnosis Safe) — 13 operation(s) for transactions.
Scroll within the panel for all 16 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Gnosis Safe Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Gnosis Safe Finops
FINOPSSemantic Vocabularies 2
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Gnosis Safe Api Context
JSON-LDGnosis Safe Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Safe (Gnosis Safe) API Rules
SPECTRALJSON Schema 65
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AllTransactionsSchema
JSON SCHEMAAllTransactionsSchemaSerializerV2
JSON SCHEMACodeErrorResponse
JSON SCHEMAContract
JSON SCHEMAContractAbi
JSON SCHEMADataDecoder
JSON SCHEMADelegate
JSON SCHEMADelegateSerializerV2
JSON SCHEMAErc20Info
JSON SCHEMAEthereumTxWithTransfersResponse
JSON SCHEMAIndexingStatus
JSON SCHEMAMasterCopyResponse
JSON SCHEMAModulesResponse
JSON SCHEMAOwnerResponse
JSON SCHEMAPaginatedAllTransactionsSchemaList
JSON SCHEMAPaginatedContractList
JSON SCHEMAPaginatedSafeCollectibleResponseList
JSON SCHEMAPaginatedSafeDelegateResponseList
JSON SCHEMAPaginatedSafeExportTransactionList
JSON SCHEMAPaginatedSafeLastStatusList
JSON SCHEMAPaginatedSafeMessageResponseList
JSON SCHEMAPaginatedSafeModuleTransactionResponseList
JSON SCHEMAPaginatedSafeMultisigTransactionResponseList
JSON SCHEMAPaginatedTokenInfoResponseList
JSON SCHEMAPaginatedTokenListList
JSON SCHEMAPaginatedTransferWithTokenInfoResponseList
JSON SCHEMASafeBalanceResponse
JSON SCHEMASafeCollectibleResponse
JSON SCHEMASafeCreationInfoResponse
JSON SCHEMASafeDelegateResponse
JSON SCHEMASafeDeployment
JSON SCHEMASafeDeploymentContract
JSON SCHEMASafeExportTransaction
JSON SCHEMASafeInfoResponse
JSON SCHEMASafeLastStatus
JSON SCHEMASafeMessage
JSON SCHEMASafeMessageResponse
JSON SCHEMASafeMessageSignature
JSON SCHEMASafeModuleTransactionResponse
JSON SCHEMASafeModuleTransactionWithTransfersResponse
JSON SCHEMASafeMultisigConfirmation
JSON SCHEMASafeMultisigConfirmationResponse
JSON SCHEMASafeMultisigTransaction
JSON SCHEMASafeMultisigTransactionEstimate
JSON SCHEMASafeMultisigTransactionEstimateResponse
JSON SCHEMASafeMultisigTransactionResponse
JSON SCHEMASafeMultisigTransactionResponseSerializerV2
JSON SCHEMASafeMultisigTransactionWithTransfersResponse
JSON SCHEMASafeOperation
JSON SCHEMASafeOperationConfirmation
JSON SCHEMASafeOperationConfirmationResponse
JSON SCHEMASafeOperationResponse
JSON SCHEMASafeOperationWithUserOperationResponse
JSON SCHEMATokenInfoResponse
JSON SCHEMATokenList
JSON SCHEMATransferWithTokenInfoResponse
JSON SCHEMAUserOperationResponse
JSON SCHEMAUserOperationWithSafeOperationResponse
JSON SCHEMAScroll within the panel for all 65 ·
Examples 60
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
About_Deployments_List
EXAMPLEAbout_Ethereum_Rpc_Retrieve
EXAMPLEAbout_Indexing_Retrieve
EXAMPLEAbout_Retrieve
EXAMPLEAbout_Singletons_List
EXAMPLEContracts_List
EXAMPLEContracts_Retrieve
EXAMPLEData_Decoder_Create
EXAMPLEDelegates_Create
EXAMPLEDelegates_Create_2
EXAMPLEDelegates_Destroy
EXAMPLEDelegates_Destroy_2
EXAMPLEDelegates_List
EXAMPLEDelegates_List_2
EXAMPLEMessages_Retrieve
EXAMPLEMessages_Signatures_Create
EXAMPLEModule_Transaction_Retrieve
EXAMPLEModules_Safes_List
EXAMPLEModules_Safes_Retrieve
EXAMPLEOperations Index
EXAMPLEOwners_Safes_List
EXAMPLEOwners_Safes_Retrieve
EXAMPLESafe_Operations_Retrieve
EXAMPLESafes_All_Transactions_List
EXAMPLESafes_Balances_Retrieve
EXAMPLESafes_Balances_Retrieve_2
EXAMPLESafes_Collectibles_Retrieve
EXAMPLESafes_Creation_Retrieve
EXAMPLESafes_Delegates_Destroy
EXAMPLESafes_Export_Retrieve
EXAMPLESafes_Messages_Create
EXAMPLESafes_Messages_List
EXAMPLESafes_Retrieve
EXAMPLESafes_Safe_Operations_Create
EXAMPLESafes_Safe_Operations_List
EXAMPLESafes_Transfers_List
EXAMPLESafes_User_Operations_List
EXAMPLETokens_List
EXAMPLETokens_Lists_List
EXAMPLETokens_Retrieve
EXAMPLETransfer_Retrieve
EXAMPLEUser_Operations_Retrieve
EXAMPLEScroll within the panel for all 60 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Safe (Gnosis Safe) — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/gnosis-safe · machine-readable index on apis.io