Exist integration: operations for AI agents
Exist connects to Type.com as an integration. This page lists the 15 operations documented for Claude and Codex in Type.com: 10 read, 5 write.
About Exist
Exist is a personal analytics app that combines data from various services to help users understand and improve their lives.
Categories: Analytics & Data
How to connect Exist to Type.com
- Access
- Organization connection: one shared account for the workspace.
To add the connection, follow the steps in Space connections.
Documented operations
15 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.
Attributes
- Read
Get attribute templates
Retrieve a list of the attribute templates Exist supports. See attribute template definition and list.
GET /api/2/attributes/templates/ - Read
Get a user's attributes
Retrieve a list of the user's attributes, without any values. Results are limited to your read scopes.
GET /api/2/attributes/ - Read
Get attributes with values
Returns a paged list of the user's attributes and their recent values. Results are limited to your read scopes.
GET /api/2/attributes/with-values/ - Read
Get a specific attribute
Returns a paged list of all values from an attribute. Results are limited to your read scopes.
GET /api/2/attributes/values/
Attribute Ownership
- Read
List owned attributes
Retrieve a list of the user's attributes, without any values. Results are limited to what your service already owns.
GET /api/2/attributes/owned/ - Write
Acquire attributes
Acquiring an attribute makes your client the owner of the attribute. This allows a service to write values for this attribute. Users do not have to approve this (mostly because this would be cumbersome) so please explain/confirm this behaviour with users within your own application. Acquiring a templated attribute the user doesn't have yet will create this attribute and give you ownership.
POST /api/2/attributes/acquire/ - Write
Release attributes
Do this to release your ownership of any attributes. The attributes' ownership will pass to another service, if the user has another supplied that has indicated it can handle this attribute, or otherwise become inactive.
POST /api/2/attributes/release/
Averages
- Read
Get averages
Returns the most recent average values for each attribute, one set per week. Can be used to retrieve historical averages for attributes also. Results are limited to your read scopes.
GET /api/2/averages/
Correlations
- Read
Get all correlations
Returns a paged list of all correlations generated in the last week, optionally filtered by attribute, strength, or confidence. Results limited to your read scopes.
GET /api/2/correlations/ - Read
Find a specific correlation combination
Takes parameters for the two related attributes and returns one or zero correlations, depending on whether Exist has found something. Will only return a result if at least one of the attributes is in your read scopes.
GET /api/2/correlations/combo/
Creating Attributes
- Write
Create new attributes
Write scopes allow your client to create new attributes for a user in the matching scopes. These attributes can be templated, or entirely custom. The manual_write scope allows creating manual attributes in any group. If you choose not to use a template, an entirely custom attribute can be defined, with its own label and value type. It must belong to an existing group.
POST /api/2/attributes/create/
Insights
- Read
Get all insights
Returns a paged list of the authenticated user's insights (see the definition). Results are limited to your read scopes.
GET /api/2/insights/
Users
- Read
Get profile for user
Returns some basic details and personal preferences for the authenticated user. No specific scope is required.
GET /api/2/accounts/profile/
Writing Data
- Write
Update attribute values
This endpoint allows services to update attribute data for the authenticated user in batches of up to 35 updates in one call. This may include, for example, 35 days of data for one attribute, or one day's values across 35 attributes. Batching updates is strongly encouraged to avoid multiple calls to the API. Data is stored on a single day granularity, so each update contains name, date, and value. Make sure the date is local to the user — though you do not have to worry about timezones directly, if you are using your local time instead of the user's local time, you may be a day ahead or behind! Valid values are described by the attribute's value_type and value_type_description fields. However, values are only validated broadly by type and so care must be taken to send correct data. Do not rely on Exist to validate your values beyond enforcing the correct type. This endpoint accepts total values for attributes and overwrites the previous value with the (validated) value you send. Non-null values cannot be set back to null, to prevent accidental data loss. Check value types for each attribute in list of supported attributes.
POST /api/2/attributes/update/ - Write
Increment attribute values
While the update endpoint requires total values to be sent for a day, the increment endpoint allows sending deltas, or the change in value to be applied to the existing value. For example, to set a value fridge_opens, a count of how many times the refrigerator door is opened for a day, the update endpoint requires storing the total each day and sending this new total each time the door is opened. In contrast, the increment endpoint is happy to accept a 1 value for fridge_opens, removing the need for the client to remember the current state. The attributes must already exist and be owned by your service. Valid values are described by the attribute's value_type and value_type_description fields. However, values are only validated broadly by type and so care must be taken to send correct data. Do not rely on Exist to validate your values beyond enforcing the correct type. This endpoint will not allow incrementing string, scale, or time of day attributes. Check value types for each attribute in list of supported attributes.
POST /api/2/attributes/increment/
No operations match.
See How connections work for access and permissions, or browse all integrations.