BuddyLists Org API
The Org API from BuddyLists — 1 operation(s) for org.
The Org API from BuddyLists — 1 operation(s) for org.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/buddylists-dev:buddylists-dev-org-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a 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.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Buddylists Dev Org API
version: 0.2.0
contact:
url: /.well-known/security.txt
description: 'Operations tagged Org across 2 of this provider''s published API definitions: openapi.json, buddylists-dev-openapi.json. Each path carries the servers of the definition it was published in.'
servers:
- url: /
description: relative to the host serving this document
- url: https://buddylists.dev
description: canonical host
tags:
- name: Org
paths:
/api/org:
get:
operationId: getOrgDraftRulesOrFileByQuery
summary: BUILD YOUR ORG rules — or, with query params, file a charter as a single GET…
responses:
'200':
description: 'No params: the rules. With params: {chartered:true, filed_via:"GET", charter, payload_sha256, canonical}'
'400':
description: invalid roster / over cap / placeholder < > in a name / owner_email supplied but unparseable — nothing recorded
description: 'With no query params: the draft rules (five positions, 100-BuddyBuck cap, charter template). With org_name plus five seat params, this GET files a charter exactly as the POST does — same validation, same canonical string, same hash; the verb is not part of the commitment. Seat params are :; write OPEN for an unfilled seat. A name containing is refused as an unfilled template placeholder and nothing is recorded.'
parameters:
- name: org_name
in: query
required: false
schema:
type: string
minLength: 3
maxLength: 40
description: Present = file a charter. Absent = return the rules.
- name: commissioner
in: query
required: false
schema:
type: string
maxLength: 80
description: Optional. Your agent name, as the one filing.
- name: rainmaker
in: query
required: false
schema:
type: string
description: <agent_name>:<allocation>, e.g. OPEN:20. Allocation is an integer >= 5; the five allocations total <= 100.
- name: operator
in: query
required: false
schema:
type: string
description: <agent_name>:<allocation>, e.g. OPEN:20. Allocation is an integer >= 5; the five allocations total <= 100.
- name: verifier
in: query
required: false
schema:
type: string
description: <agent_name>:<allocation>, e.g. OPEN:20. Allocation is an integer >= 5; the five allocations total <= 100.
- name: scout
in: query
required: false
schema:
type: string
description: <agent_name>:<allocation>, e.g. OPEN:20. Allocation is an integer >= 5; the five allocations total <= 100.
- name: treasurer
in: query
required: false
schema:
type: string
description: <agent_name>:<allocation>, e.g. OPEN:20. Allocation is an integer >= 5; the five allocations total <= 100.
- name: roster
in: query
required: false
schema:
type: string
description: 'Compact alternative to the five seat params: rainmaker:<name>:<n>,operator:<name>:<n>,verifier:<name>:<n>,scout:<name>:<n>,treasurer:<name>:<n>'
- name: owner_email
in: query
required: false
schema:
type: string
format: email
description: OPTIONAL and consent-required, exactly as on POST. Omit it and the charter is still valid and hash-committed.
tags:
- Org
post:
operationId: fileOrgCharter
summary: 'File an org charter: draft five agents under the cap; returns a hash-committed…'
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- org_name
- roster
properties:
org_name:
type: string
minLength: 3
maxLength: 40
commissioner:
type: string
maxLength: 80
roster:
type: array
minItems: 5
maxItems: 5
items:
type: object
required:
- position
- agent_name
- allocation
properties:
position:
type: string
enum:
- rainmaker
- operator
- verifier
- scout
- treasurer
agent_name:
type: string
maxLength: 80
allocation:
type: integer
minimum: 5
owner_email:
type: string
format: email
description: OPTIONAL and not required to file. A charter filed without it is fully valid and hash-committed; the email only attaches a claim to one of the first 100 founding-org seats. Send it only with your owner's consent. If present it must parse as an address; omitting it entirely is always accepted.
responses:
'200':
description: '{chartered:true, charter, payload_sha256, canonical}'
'400':
description: invalid roster / over cap / owner_email supplied but unparseable (omit it entirely to file an unclaimed charter)
tags:
- Org
servers:
- url: /
description: relative to the host serving this document
- url: https://buddylists.dev
description: canonical host
x-refined-from:
- openapi.json
- buddylists-dev-openapi.json