Your knowledge, ready for your agents.
Keep useful notes here. Connect your agents, then pick up where you left off.
Make your first handoff
Setup: 0 of 4 done
A connection enables access. Verify a useful answer in each agent before relying on a handoff.
Working with a team?
Create a project and share only the knowledge you choose.
Sign in to continue
This page is part of your private workspace. Sign in and you will return here.
Linked mentions
Registrations
Review requests for agent access and keep track of everyone who has signed up. Approval allows a person to connect agents to their own workspace. Open Billing on a card to see a person's plan or grant a complimentary one.
Usage holdings
Note and storage limits compare against each account's stored holdings. Check measures every account against its notes and files and changes nothing. Repair sets each account that differs to what was measured. Run both before turning on usage enforcement.
Daily usage report
One UTC day of metered use per plan ceiling, and its would-deny: the operations shadow mode counted past a ceiling and let through. Under enforcement an agent request or a note save past its ceiling is refused with an error, while a semantic search past its ceiling is answered from keywords instead, so its would-deny is a degraded search, not a refusal. Read it through the shadow week before turning enforcement on. Holdings past a plan's ceiling are shown as they stand now, not for the day.
Provider work
Paid Workers AI and Vectorize work per UTC day, counted as it is sent, whether or not the call succeeded: embedding calls and the texts sent to them, Vectorize queries and the matches they returned, Vectorize upserts and the vectors sent, reranker calls and the passages sent. Counts only, never content. This is the evidence for the global ceilings (CAP-01C C5): a day at or past an operation's ceiling is flagged, and past it the Worker answers searches from keywords, skips the reranker or leaves chunks pending until the next UTC day.
Signup funnel
For each UTC day: the sign-in requests accepted and those refused before any email by the rate limit, the bot check or membership (the same request starts a sign-in and a sign-up, so these are attempts, not new people), the accounts created, and how far the accounts created that day have come since: an agent connected, an agent made a request, two agents made requests, and a checkpoint was saved. A checkpoint counts when it is a project checkpoint the person authored or was saved in a workspace only they belong to; one saved in a workspace with several members cannot be tied to a person and is not counted. Counts only, from records Allbase already keeps. Website visits and where people came from are not collected, so they are not here.
Allbase catalog
Curated skills every approved person and their agents can read. Only releases an operator published into the catalog workspace can be listed.
Settings
Identity
Shown to people who know you — invite emails, contacts, workspace members. Never on the public directory.
Your public name on the directory and publications. Lowercase letters, digits, single hyphens.
Import & export knowledge
Everything you keep here stays yours as ordinary Markdown. Export a ZIP of every current note with paths, frontmatter, and wikilinks intact; it opens as an Obsidian vault and re-imports cleanly. A workspace above 2,000 notes exports as several ZIP parts of up to 2,000 notes each. Import a ZIP or an exported vault to bring notes in.
Account
Leave Allbase
Permanently delete your account, every workspace only you belong to, and everything in it: notes, revision history, uploaded files, memories, checkpoints, search and embedding data, and agent credentials. Export a copy first if you want one. This cannot be undone.
Project checkpoints remain in the project's history if the project survives your departure. Deleting your personal workspace does not remove that project history.
Billing
Allbase Individual costs $15 per month when purchased through Stripe. Your knowledge remains available to read and export if your plan changes.
Allbase Max costs $45 per month, with 10× the Individual limits.
- Plan
- Loading…
- Subscription
- Loading…
Checking billing availability…
About you — the user/ folder
Background your agents receive when they start work. The first ~2,000 characters of user/user.md are injected at every bootstrap — lead with what matters. Files under user/ can never be shared or published.
Organizations
An organization is the root that owns shared projects, teams, and shares so they outlive any one person. You are the admin of your own. Joining someone else's places your account under its admins: they can suspend it, revoke its agents and sessions, and reassign what you own there. Your personal workspace stays yours.
Sessions
Skills
Keep reusable procedures and their supporting files together. Each import saves one complete, retained draft.
From Allbase
Skills Allbase publishes for everyone. Install one into a project with your local agent; your own skills stay private below.
Installed, since withdrawn
Your skills are private to you and your authorized agents. Importing stores files; it does not publish, install, run scripts, or grant access to knowledge.
Kits
A kit bundles agent blueprints with the skills they use. Import a kit folder from your workspace, review it, then publish a private version your agents can install.
Import with your connected agent
Ask your agent to inspect a skill directory and import it as a private Allbase draft. The local helper captures original bytes and executable flags, shows a review plan, and uploads only after you apply it.
For example, a review-notes/ folder with SKILL.md and a supporting checklist. The SKILL.md name must match the folder name. ZIP input and managed installation are not part of private draft import.
Revision
Validation and review findings
Files in this revision
Revision history
Declarations and provenance
Declarations do not grant permissions or prove agent app compatibility.
Package SHA-256
Original source SHA-256
Releases
Your agents
Connect your tools once. See what each agent can access and whether it has used your knowledge.
Bring your next agent up to speed.
Choose your agent app, approve its connection, then verify it can find a note.
Connection & context health
Connection is access. A successful retrieval is evidence of use.
Verify an agent with your knowledge
Choose a saved note, copy the prompt into the agent you want to check, then refresh status here. Confirm the returned citation supports its answer.
This page never calls an agent on your behalf. An empty search, an OAuth connection, or a refresh is not a successful knowledge handoff.
Manage connections and permissions
Advanced: API credentials
Agents connect with OAuth through the installer at
https://allbase.md or the Connect page, with no token to copy.
New agent credentials are retired; existing ones keep working until you sign them out.
Projects
Pick up where your agents left off. Projects with saved checkpoints appear here automatically.
Project members and their agents can read the project's checkpoints, tasks and folders at their role. Open a project to see its activity, its knowledge and its people, and to invite someone.
Create a project
Name new work, or use an existing project key to add a name and invite people. Existing checkpoint history for that project key becomes part of the project and is available to its members.
Each project gets a home folder in your workspace, projects/<key>/. Everyone you add to the project can read the notes you keep there, and contributors can edit them. Nothing else in your workspace is shared.
Only the people you select can review this knowledge. It enters their agents' retrieval after they accept. Read & write lets them edit the same source.
Add a trusted contact before inviting them. Contacts and team membership alone never expose personal notes.
Memory from your notes
Inspect the knowledge your agents can recall. Every memory links to its source; you can correct it or require review.