Getting Started

Connect your first agent to Blocks Enterprise and share it with your team.

Prerequisites

• Access to your Blocks Enterprise instance (https://your-company.blocks.ai)
• User account in at least one organization
• Blocks CLI installed

1. Connect your agent

If you're creating a new agent, initialize the agent:

blocks init my_agent_name --mode provider --yes --language node

Use --language python for Python. If you have an existing agent, you can skip initialization.

Navigate to your new agent directory:

cd my_agent_name

Authenticate with your Enterprise deployment:

blocks login https://your-company.blocks.ai/ --write-env

This opens your browser for authentication and writes credentials to .env in the current directory. To verify your login, run blocks whoami. If you belong to multiple organizations, you'll be prompted to select one during login. To switch organizations later, run blocks login again and select a different organization.

Install dependencies:

For Node.js:

npm install

For Python:

python -m venv venv

source venv/bin/activate  # On Windows PowerShell: .\venv\Scripts\Activate.ps1

pip install -e .

2. Register the agent

Register your agent to make it available in your Enterprise deployment:

blocks register

This creates a private agent owned by your current organization. Members of your organization and explicitly shared users/orgs can access it. To make an agent visible to everyone in your company, run blocks publish and select "Public" when prompted for the listing visibility. By default, agents are private (visible to owner org and explicitly shared users/orgs). Publishing as public makes them visible to all authenticated users in your deployment. Both private and public agents are private to your company—Enterprise agents never appear on Blocks Network marketplace.

3. Run the agent

Start your agent so others can use it to the Enterprise deployment:

blocks run

Your agent is now connected and ready. Keep this running.

4. Share your agent

You can invite users or organizations via CLI or through your agent's page in the UI.

Note: Invitations must be accepted before granting access. User invitations require acceptance by the invitee. Organization invitations require acceptance by a member with org:manage permission.

To invite a specific user:

blocks invite send my_agent_name --email user@example.com

To invite an entire organization:

blocks invite send my_agent_name --org org-slug

To share with another agent (agent-to-agent communication):

blocks invite send my_agent_name --email other_agent_name@blocks.ai

See Manage access to private agents for invitation workflows and permissions.