People & companies
Understand who is involved
Retrieve people, company context, teams and the relationships around the account, within the connected user's access.
Agent access
Better models still need to know your business.
Give models and agents the context behind the work. Ishara serves people, companies, relationships and account history through API and MCP, under your enterprise permissions.
Permissioned knowledge · Evidence-linked actions
Business context, connected
Give the agent something useful to know
History & commitments
Remember what matters
Read meeting history, open follow-ups, deal context, mail metadata and pre-meeting reports in the same connected picture.
Records & working sets
Work with your business model
Access records, custom objects, saved lists, notes and tasks through the object interface, with the permissions those records already carry.
A better next move
From an answer to an action you can review
An agent can propose a change with a reason and supporting evidence. The preview shows the values before and after, so your team can decide what should become part of the record.
Review is the default. Administrators can explicitly allow scoped, low-risk actions to apply automatically.
Explore AI in IsharaExample workflow
Prepare the account follow-up
- Read the context. Recover the relationship, meeting history and open commitments.
- Propose the next step. Present a task or record change with its reason and evidence.
- Review and apply. Check what will change before it lands in the account.
Every proposal stays within the connected user's permissions.
Access you control
Your rules travel with the context
The right identity
An API key acts as its owner, in that person's workspace. The existing record permissions determine what the agent can read.
A defined scope
Choose the access the connection needs. Proposing and applying changes have their own permissions.
A visible trail
Context requests and applied proposals are recorded. Your team can see the action and the access behind it.
Built on connected knowledge
Bring the outside world and your history together
Public intelligence explains the market. Private enterprise context explains the relationship. Ishara makes the relevant context available to people, models and agents through one permissioned knowledge layer.
Frequently asked questions
How do agents connect to Ishara?
Through Ishara's API and MCP interfaces. A connection uses a user-provided Ishara API key, and its requests run as that key's owner under the owner's workspace permissions and granted scopes.
What context can an agent read?
The supported context includes people, companies, teams, relationship and meeting history, open follow-ups, mail metadata, deals, pre-meeting reports and context bundles. The object interface also exposes records, lists, notes, tasks and interactions when the key has the required access.
Can an agent change our records?
Agents can propose changes with a reason, evidence and a preview. Review is the default; applying a proposal needs the appropriate permission. A workspace administrator may explicitly allow a limited set of low-risk operations to apply automatically.
Does an agent receive more access than its user?
The API key acts as its creator, and access is checked against that person's permissions. Scopes can narrow the connection further, and the workspace can switch context sharing off.
Give your AI the context it needs.
Connect enterprise knowledge to the people and agents doing the work.
Public intelligence · Private enterprise context · Agent access