Buftechnologies

Buftechnologies API

Buftechnologies API as documented publicly: 3 operations. Contract generated from the documentation by API Evangelist (2026-10-06); not the provider's own document.

Documentation GitHub OpenAPI

Operations 3

GET /connectrpc.eliza.v1.ElizaService/Converse GET /connectrpc.eliza.v1.ElizaService/Converse #

POST /connectrpc.eliza.v1.ElizaService/{connectrpcelizav1elizaserviceid} POST /connectrpc.eliza.v1.ElizaService/Introduce #

GET /foo.bar.v1.FooService/DoSomething GET /foo.bar.v1.FooService/DoSomething #

Specifications

⚙

OpenAPI

https://raw.githubusercontent.com/api-evangelist/buftechnologies/refs/heads/main/openapi/_ae-authored/buftechnologies-openapi-generated.yml

Schemas & Data

📊

JSONSchema

https://raw.githubusercontent.com/api-evangelist/buftechnologies/refs/heads/main/json-schema/buftechnologies-post-connectrpc-eliza-v1-elizaservice-connectrpcelizav1-elizaservi-schema.json

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/buftechnologies:buftechnologies-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.1.0
info:
  title: Buftechnologies API
  version: '2026-10-06'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-06: 3 operation(s) read from 3 public documentation page(s) (each operation
    names its page in x-source). This is not the provider''s published contract; Buftechnologies has published no machine-readable contract that
    the pipeline could find. Engine: local.'
  x-evidence-tiers:
    code-example: 4
    documentation: -1
    pages-with-code: 3
    pages-read: 3
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-10-06'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://buf.build/docs/bsr/apis/api-access
  - https://buf.build/docs/bsr/apis/mcp
  - https://buf.build/docs/reference/cli/buf/curl
servers:
- url: https://demo.connectrpc.com
paths:
  /connectrpc.eliza.v1.ElizaService/Converse:
    get:
      operationId: get_connectrpc_eliza_v1_ElizaService_Converse
      tags:
      - Connectrpc
      summary: GET /connectrpc.eliza.v1.ElizaService/Converse
      x-source: https://buf.build/docs/reference/cli/buf/curl
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl --data @- --header @- --protocol grpcweb  https://demo.connectrpc.com/connectrpc.eliza.v1.ElizaService/Converse  <<EOM\n\
          \ Custom-Header-1: foo-bar-baz \n Authorization: token jas8374hgnkvje9wpkerebncjqol4 \n {\"sentence\": \"Hi, doc. I feel hungry.\"}\
          \ \n {\"sentence\": \"What is the answer to life, the universe, and everything?\"} \n {\"sentence\": \"If you were a fish, what of fish\
          \ would you be?.\"} \n EOM \n N"
  /connectrpc.eliza.v1.ElizaService/{connectrpcelizav1elizaserviceid}:
    post:
      operationId: post_connectrpc_eliza_v1_ElizaService_connectrpcelizav1elizaserviceid
      tags:
      - Connectrpc
      summary: POST /connectrpc.eliza.v1.ElizaService/Introduce
      x-source: https://buf.build/docs/reference/cli/buf/curl
      parameters:
      - name: connectrpcelizav1elizaserviceid
        in: path
        required: true
        schema:
          type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PostConnectrpcElizaV1ElizaserviceConnectrpcelizav1Elizaservi'
      responses:
        '201':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl --schema buf.build/connectrpc/eliza  --data '{\"name\": \"Bob Loblaw\"}'  https://demo.connectrpc.com/connectrpc.eliza.v1.ElizaService/Introduce\n\
          \ Issue a unary RPC to a server that supports reflection, with verbose output: "
        collapsed_from: 2 example path(s) differing only at connectrpcelizav1ElizaServiceId
  /foo.bar.v1.FooService/DoSomething:
    get:
      operationId: get_foo_bar_v1_FooService_DoSomething
      tags:
      - Foo
      summary: GET /foo.bar.v1.FooService/DoSomething
      x-source: https://buf.build/docs/reference/cli/buf/curl
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl --schema . --protocol grpc --http2-prior-knowledge  http://localhost:20202/foo.bar.v1.FooService/DoSomething\n Issue an\
          \ RPC to a Connect server, where the schema comes from the Buf Schema Registry, using\na request that is defined as a command-line argument: "
components:
  schemas:
    PostConnectrpcElizaV1ElizaserviceConnectrpcelizav1Elizaservi:
      type: object
      properties:
        name:
          type: string
tags:
- name: Connectrpc
- name: Foo