Keep a customer’s profile details clear before creating or updating a record.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Read a known customer and organize its contact and metadata details.
/oo Checkout.com: Read Checkout.com customer [customer ID or email]. Summarize its identifier, email, name, phone and metadata where present. Identify missing details needed for [business purpose], without expanding payment instrument information beyond what is necessary.
Apply an exact contact or metadata correction to a selected record.
/oo Checkout.com: Read Checkout.com customer [customer ID], then update only these fields [exact email, name, phone or metadata values]. Keep other fields unchanged and report whether the update was accepted. Read the profile again to show the resulting selected fields.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect with a Checkout.com secret API key, matching sandbox or production environment, and endpoint prefix.
Connect Checkout.com →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
Create, read and update customer records in Checkout.com. AI can summarize a known profile and apply your specified contact or metadata changes; payment collection and transaction reporting are outside this connection.
Read one customer by identifier.
Create a customer or update explicitly supplied fields.
Create a Checkout.com customer for storing reusable customer details.
Leina 
Wanta 
checkout_com.create_customer Get a Checkout.com customer and their linked payment instruments by ID or email.
checkout_com.get_customer Update stored details for a Checkout.com customer.
checkout_com.update_customer Delete a Checkout.com customer and all linked payment instruments.
checkout_com.delete_customer No matching tools.
Provide a known customer ID or email for the profile lookup. There is no customer-list operation in this connection.
Provide an email address and any intended name, phone or metadata. The operation returns the created customer ID; it does not create a payment or charge.
After an accepted update, read the same customer ID again and compare the selected fields with the requested values. Use the same connected environment for both operations.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.