Create Contact
create_personAdd a Dayze Contacts record, birthday included (YYYY-MM-DD, YYYY-MM, YYYY, or MM-DD if year unknown); checks duplicates first. An existing contact comes back unchanged with its person_id, not_applied (the fields you sent) and a hint. request_id is optional: without one, identical calls within 15 minutes return the first result. Advertised name create_person is stable; tools/call also accepts create_contact. ($0.10; API key required)
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>"
},
"name": "create_person"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Display name, e.g. Alex Chen. | |
| tier | No | Relationship priority: vip, normal or low, e.g. vip. | |
| No | email. Omit to leave unchanged; null or blank clears. | ||
| notes | No | Free-text note, e.g. Follow up next week. | |
| phone | No | phone. Omit to leave unchanged; null or blank clears. | |
| aliases | No | Alternate names stored as aliases, e.g. ["Lex","Alex C"]. | |
| company | No | company. Omit to leave unchanged; null or blank clears. | |
| wallets | No | PHI-930: ENS (.eth) / SNS (.sol) names and/or addresses for this contact. Stored in social_handles (legacy ens/ens_address kept). | |
| birthday | No | YYYY-MM-DD, YYYY-MM, YYYY, or MM-DD / --MM-DD when the year is unknown (same as update_person) | |
| occupation | No | Occupation / job title. Omit to leave unchanged; null or blank clears. | |
| request_id | No | Client idempotency key (retries return original result). | |
| is_favorite | No | Mark the contact as a favorite, e.g. true. | |
| context_tags | No | Context tags such as Work, Personal or Family, e.g. ["Work"]. | |
| relationship | No | Relationship label, e.g. friend or sister. | |
| relationships | No | Who they are to the user, primary first, e.g. ["friend","colleague"]. | |
| idempotency_key | No | Alias for request_id. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | ||
| code | No | ||
| hint | No | ||
| name | No | ||
| slug | No | ||
| No | |||
| phone | No | ||
| people | No | ||
| person | No | CRM person record. | |
| account | No | The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer. | |
| aliases | No | Aliases saved on the new contact. | |
| changed | No | ||
| company | No | ||
| created | No | ||
| message | No | ||
| skipped | No | ||
| wallets | No | ||
| birthday | No | As stored: YYYY-MM-DD. A year-unknown birthday is 1900-MM-DD (Feb 29: 1904-02-29). | |
| duplicate | No | True when the contact already existed: nothing on it was changed. | |
| person_id | No | The new contact, or the existing one on a duplicate. | |
| candidates | No | ||
| created_at | No | ||
| occupation | No | ||
| person_ids | No | ||
| provenance | No | Which connector wrote the record and which connected Dayze account received it. | |
| inspect_url | No | The Dayze page that shows the saved record. | |
| matched_via | No | ||
| not_applied | No | On a duplicate: the fields sent that were not saved. | |
| role_expand | No | ||
| inspect_note | No | What inspect_url opens. Never quote the record id. | |
| hygiene_flags | No | ||
| aliases_not_saved | No | Aliases not saved (another contact has them); the contact was still created. | |
| idempotent_replay | No | ||
| birthday_precision | No | day, month, year, month_day (year unknown) or approximate. | |
| needs_clarification | No | Ask which contact the user means; no contact was created or changed. |