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

H2O.ai Memory Blocks API

The Memory Blocks API from H2O.ai — 9 operation(s) for memory blocks.

H2O.ai Memory Blocks API is one of 26 APIs that H2O.ai publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Memory Blocks. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and a changelog.

This API exposes 15 operations across 9 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version v1.0.0.

Requests are made against a single base URL, https://h2ogpte.genai.h2o.ai/api/v1.

15 operations 9 paths 12 schemas 3 DELETE6 GET1 POST5 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1.0.0
Base URL
https://h2ogpte.genai.h2o.ai/api/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

H2O.ai Memory Blocks API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Using an API key generated by H2OGPTe

Paths & Operations 15

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

Memory Blocks 15
GET
/users/current/default_memory_blocks
Get default memory blocks
get_default_memory_blocks → 200400401404default
PUT
/users/current/default_memory_blocks
Set a default memory block
set_default_memory_block body → 200400401404default
POST
/memory_blocks
Create a Memory Block
create_memory_block body → 201400401404409default
GET
/memory_blocks
List memory blocks
list_memory_blocks 4 params → 200400401default
GET
/memory_blocks/{memory_block_id}
Get a memory block by ID
get_memory_block 1 param → 200400401404default
PUT
/memory_blocks/{memory_block_id}
Update a memory block
update_memory_block 1 param body → 204400401403404409default
DELETE
/memory_blocks/{memory_block_id}
Delete a memory block
delete_memory_block 1 param → 204400401403404409default
GET
/memory_blocks/{memory_block_id}/permissions
List user share permissions for a memory block
list_memory_block_permissions 1 param → 200401403404default
GET
/memory_blocks/{memory_block_id}/group_permissions
List group share permissions for a memory block
list_memory_block_group_permissions 1 param → 200401403404default
PUT
/memory_blocks/{memory_block_id}/group_permissions/{group_id}
Share a memory block with a group
share_memory_block_with_group 2 params body → 204401403404default
DELETE
/memory_blocks/{memory_block_id}/group_permissions/{group_id}
Remove sharing of a memory block from a group
unshare_memory_block_from_group 2 params → 204401403404default
PUT
/memory_blocks/{memory_block_id}/permissions/{username}
Share a memory block with a user
share_memory_block 2 params body → 204400401403404409default
DELETE
/memory_blocks/{memory_block_id}/permissions/{username}
Remove sharing of a memory block from a user
unshare_memory_block 2 params → 204400401403404409default
GET
/memory_blocks/{memory_block_id}/public_permissions
Returns the public permissions for a memory block
list_public_memory_block_permissions 1 param → 200401default
PUT
/memory_blocks/{memory_block_id}/privacy
Set memory block public or private
set_memory_block_privacy 1 param body → 204400401403404409default

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are MemoryBlock (16 properties), MemoryBlockUpdateRequest (6 properties), MemoryBlockCreateRequest (6 properties), MemoryBlockPrivacyRequest (2 properties). Each schema is shown below with its type and property counts.

MemoryBlockCreateRequest
object
6 properties 1 required
DefaultMemoryBlocksByScope
object
2 properties
ShareMemoryBlockRequest
object
1 property
SetDefaultMemoryBlockRequest
object
2 properties 1 required
MemoryBlockUpdateRequest
object
6 properties
MemoryBlock
object
16 properties 9 required
MemoryBlockPrivacyRequest
object
2 properties 1 required
DefaultMemoryBlocksResponse
object
1 property
SetDefaultMemoryBlockResponse
object
2 properties
GroupSharePermission
object
2 properties 1 required
SharePermission
object
2 properties 1 required
EndpointError
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

h2o-ai-memory-blocks-api-openapi.yml Raw ↑

Other APIs H2O.ai publishes across the network.

h2oGPTe MCP Server
H2O.ai Admin Sessions API
H2O.ai Agents API
H2O.ai AI Assistants API
H2O.ai API Keys API
H2O.ai Chat API
H2O.ai Collections API
H2O.ai Configurations API
H2O.ai Document Ingestion API
H2O.ai Documents API
H2O.ai Extractors API
H2O.ai Forums API
Where this information came from

This is an independent, third-party profile of H2O.ai Memory Blocks 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.