Assistant connector
Ask your assistant for the data, instead of asking us.
Connect TalkDataToMe to Claude, ChatGPT, Grok, or anything else that speaks the Model Context Protocol. Then run counts, order lists, append phone numbers and check your usage from inside the tool you already work in. No key to paste, no email thread, no waiting on us.
Setting it up
One URL, and a sign-in. The whole thing takes about a minute.
https://www.talkdatatome.online/api/mcp- 1
Add the connector in your assistant
In Claude, open Settings, then Connectors, then Add custom connector, and paste the URL above. In ChatGPT it is Settings, then Connectors. In Grok it is grok.com/connectors, then New connector, then Custom. Leave every other field empty.
- 2
Sign in when it sends you to us
Your assistant opens our sign-in page. Use the same email and password you use for TalkDataToMe. You are not creating anything new.
- 3
Read the approval screen, then approve
We show you which assistant is asking, which account it will act on, and exactly what it will be able to do. Approve it and you land back in your assistant, connected.
- 4
Ask it something
Start with one of the examples below. If your assistant says it cannot see the tools, disconnect and reconnect it once; some clients cache the old state.
It is already on for your account
Every TalkDataToMe account can connect an assistant. There is nothing to request and nothing to wait for. Once you are signed in, the Assistant tab shows the same steps plus what your own account can do, and lets you disconnect anything you have connected.
How the sign-in works
The connection uses OAuth 2.1 with PKCE. In plain terms: you sign in on our site, not in your assistant, and your password is never seen by the assistant or by us in that exchange. What the assistant receives is a token scoped to your account, which we store only as a one-way hash. Nobody, including us, can read it back out.
The token expires after 30 days and refreshes itself quietly in the background. You can end the connection at any time on the Assistant tab in your account, or from inside the assistant. Ending it takes effect immediately, and you can see every live connection and when it was last used.
If you run something that cannot do a sign-in flow, an account API key still works. Send it as X-API-Key or as Authorization: Bearer. You can issue one from your account settings.
What it can do
66 tools. Every one of them is labelled so your assistant knows which are free and which spend something, and a good assistant will ask you before it spends. Nothing here can delete anything or touch your billing. The one tool that can change a feed shows you the measured impact first and only applies after you say yes.
Your assistant is shown the ones your account can actually use. Counts, estimates, account reads and reporting work for everybody. Ordering records follows whatever your account is already set up to order over the API, and the licensed files (bureau credit triggers, hiring signals) follow your licence. A tool your account cannot use is hidden rather than offered and then refused. The Assistant tab lists yours exactly.
| Tool | What it does | Cost |
|---|---|---|
List the API keys on this account list_api_keys | See every API key on the account with its label, status, what it is used for and which vertical its lookups are recorded against. | Free |
Create an API key create_api_key | Issue a new API key after answering what it will do with each lookup and which vertical those people are in market for, so every lookup is recorded as a trigger for that vertical. The key is shown once. | Free, creates a key |
Set what an API key is for set_api_key_purpose | Change a key's use case, vertical or label, or switch signal recording on or off for it. | Free, changes a key |
Pause or resume an API key pause_api_key | Pause a key so calls with it are refused, or resume it. Nothing is deleted. | Free, changes a key |
Search targetable topics search_topics | Search roughly 50,000 targetable audiences and intent topics, so you can see what can be targeted before you price anything. | Free |
Count records count_records | Ask a question and get a count back. Either how many records exist matching filters (geography, age, credit, income, homeowner, dwelling, language, phone or email on file, in-market intent), or how many of your OWN records we can match and enrich, from a list you pass in or a database you already uploaded. Returns people and households separately plus per-field fill counts, and never returns personal data. | Free |
Company hiring signals company_hiring_signals | Monthly hires and departures at a company from employment history, with the senior, sales and engineering mix, growth versus a year earlier, and recent senior arrivals and departures. Switched on per account. | Free |
Estimate credit trigger records estimate_credit_triggers | Count people on the daily credit trigger file by trigger-date window, FICO band, geography, open mortgage, mobile phone and age. Licensed per account. | Free |
Order a credit trigger file submit_credit_trigger_pull | Deliver a CSV of credit trigger records with name, address, typed phone, DNC flag, email, FICO, trigger date and open mortgage trades. Never SSN or date of birth. Spends records. | Spends records |
Estimate aged form fills by date estimate_aged_form_fills | Count people who filled out a form for a vertical (mortgage, refi, solar, home services, insurance, warranty, tax debt, roofing, windows, bathroom) by form-date window, geography, phone, email and consent cert. | Free |
Order an aged form-fill file submit_aged_form_fill_pull | Deliver a CSV of aged form fills, one row per person, with name, address, phone, email, the supplier's form date, the consent cert and the loan and property fields the supplier sent. The URL and IP columns come in two flavours that are never mixed: Supplier_* is the lead's own, and Appended_* is opt-in evidence we add from our own graph for the same person, which describes a different event and is not this lead's consent. Never a date of birth. Spends records. | Spends records |
Estimate audience size estimate_audience | Count how many homeowner records match a set of ZIPs and filters, including whether they have a cell phone or an email. | Free |
Estimate intent audience size estimate_intent_audience | Count how many people are actively in market for a topic and can be delivered, across whole states rather than a ZIP list, with your age, income, phone and email filters already applied. | Free |
Estimate a property-filtered homeowner audience estimate_property_audience | Count homeowners by home value, year built, household income and equity, with a callable versus do-not-call split. | Free |
Order a list submit_pull | Order a list. You get an order id back, and the finished file is emailed to your account. | Spends records |
Order a property-filtered homeowner list submit_property_pull | Order the homeowner list with those property filters. Do-not-call numbers arrive flagged in their own column, never silently removed. | Spends records |
Estimate aged opt-in auto by vehicle estimate_aged_optin_auto | Count opted-in auto insurance and warranty records by the vehicle the consumer put on their own form, sized for direct mail. | Free |
Order an aged opt-in auto list submit_aged_optin_auto_pull | Order a direct mail file of aged opt-in auto records, filtered on year, make and model. | Spends records |
List recent orders list_pulls | Check the status and record count of your recent orders. | Free |
Get a finished list download get_pull_file | Get the download command for a finished order. | Free |
Append phone numbers append_phones | Append phone numbers to a list you already have, and see how many of them matched. | Spends records |
Look up one person resolve_identity | Look up one person by phone number or hash. There is a mode that returns a pass or fail with no personal data at all. | Spends records |
Look up properties by address lookup_properties | Send street addresses, get those properties back. The address is the key, so there is no chance of a same name mix up, and every answer says how it matched. | Spends records |
Describe your data feeds list_feeds | Your data feeds in plain English: what each one delivers, where the records come from, every active filter, the cap, the schedule, and who changed what recently. | Free |
Change a feed's age floor change_feed_targeting | Adjust or remove the minimum age a feed delivers. Your assistant shows you the measured volume impact first and only applies the change after you say yes. | Free, changes a feed |
Pause a feed pause_feed | Stop a feed delivering, right away. Nothing is deleted and nothing is lost, so you can switch it back on whenever you want. | Free, changes a feed |
Switch a paused feed back on resume_feed | Ask for a paused feed to start delivering again. You get a one tap approve link by email, and it goes live the moment you approve. | Free, changes a feed |
Set how many records a feed delivers per run set_feed_daily_cap | Turn a feed up or down by setting the most records it may send in one run, anywhere up to what your plan covers. | Free, changes a feed |
Check ad audience delivery by day audience_delivery_report | For each of your ad audiences, how many new people went out on each day: whether it delivers every day, what it averages, and when it last sent. Counts only, never records. | Free |
Count your identified website visitors estimate_website_visitors | How many real people the website pixel identified on your own site, filtered by state, city, ZIP, age, household income, the pages they looked at, or how recently they were there. Distinct people, not visits, so somebody who came back ten times counts once. Counts only, never records. | Free |
Download your identified website visitors submit_website_visitor_pull | Take your identified visitors as a file: one row per person with name, email, street address, city, state, ZIP, age, household income, when they first and last visited, and the pages they looked at. You get a secure link, and the records come off your balance. | Spends records |
Check usage and balance get_usage | Records used this month, your monthly limit, and your prepaid balance. | Free |
Records sent, received, and billed get_record_ledger | What actually moved this month: records we delivered to you, records you sent us, and what is billable. This is the one to check an invoice against. | Free |
Check feed supply check_feed_supply | See how many records a day really exist for a vertical and source before you promise a feed volume. Free, and the same check the setup wizard runs. | Free |
List saved pulls list_saved_pulls | See the pulls you saved in Chat, with whether each can run as a scheduled feed. A feed built on a saved pull has to name one of these; the setup refuses a name that was never saved. | Free |
What a delivered row will look like preview_data_feed | Five sample rows in the exact shape a feed would deliver, the column list, and any field you picked that the source cannot carry. Sends nothing, creates nothing. | Free |
Send five real rows to the destination test_data_feed | Really post, email or upload five sample rows to the destination you chose. The only thing that proves a URL, a mailbox or a credential works before the first real run. No feed is created. | Free, sends a real test |
Create a data feed (paused) create_data_feed | Set up a scheduled data feed the same way the website wizard does. It is created paused, and nothing delivers or bills until you review it and switch it on yourself. | Spends records |
Ask for a paused feed to be switched on request_feed_go_live | The last step after creating a feed. It files an approval and emails the account owner a one-tap link; the feed stays paused until they tap it. It does not start deliveries by itself. | Free, changes a feed |
Lists you can report revenue on list_reportable_lists | Every list we sent this account in a window: feed deliveries, ordered files and ad audience months, each with its List_ID, record count and what has been reported on it so far. | Free |
Report revenue on a list report_revenue | File what a list earned against its List_ID. Re-sending a list revises the figure instead of adding a second one. Spends nothing; it writes a revenue report to your account. | Free, files a report |
What needs this account account_actions | Everything waiting on you right now, most urgent first: a revenue share figure that is due or overdue, a campaign that stopped delivering, a prepaid balance running low. Each one says what it is and where to resolve it. | Free |
This account, whole picture account_overview | The whole Overview page in one call: what needs you, every data feed and ad campaign with its health and volumes, what is being received from you, API usage and the records in and out for the window. | Free |
Ad audiences left on a one-time push stale_ad_audiences | Your ad audiences that are built from interest signals but set to push once, so the platform is targeting a list that goes stale while every status reads as healthy. Says which to switch to a daily refresh and which a daily job already keeps fresh. Changes nothing. | Free |
Prepaid balance get_balance | What is on your prepaid balance, the per record rate it is drawn down at, and how many more records that buys. | Free |
Add funds to the prepaid balance add_funds | Get a secure card link to add money to your balance. Nothing is charged by asking for the link: you open it and pay, and the balance goes up once the card clears. | Free, returns a card link |
Ad campaign spend, and the audiences it ran on campaign_spend_report | What each of your ad campaigns spent in a window, day by day, with the split across the audiences we deliver. Streaming TV reports spend against the audience it ran on, so you can see what a list actually cost. Money and counts only, never records. | Free |
See which customer lists a feed holds back get_feed_suppression | Check which of your saved customer lists a feed is matching against, and whether it is matching on phone numbers, street addresses or email addresses. | Free |
Choose whether a customer list applies to a feed set_feed_suppression | Point one of your saved customer lists at a feed so it stops sending you people you already have, or take the list back off again. | Free, changes a feed |
Estimate the best records in your own database estimate_ranked_selection | Rank a database you uploaded against an offer and see the tier breakdown of the best N of it, plus how many of your records are rankable at all. | Free |
Order the best records in your own database stage_ranked_selection | Order the best N records of a database you uploaded, ranked into tiers with a score and a reason on every row. Held for release before anything is charged. | Spends records |
Ranked selections on this account list_ranked_selections | Your ranked selections, newest first, with each one's tier breakdown, list id, and whether it is still held for release. | Free |
Your uploaded databases list_my_databases | The databases you uploaded, with row counts, how many matched a person, and the columns of your own each one can be filtered on. | Free |
Create a database from records create_my_database | Create a database from an array of records and match it to people. Any key that is not an identity field is kept as a column of your own, so one file can carry every client you serve. | Free, creates a database |
Count who in your database is in market estimate_my_database_in_market | How many people in one of your databases are in market for a topic right now, narrowed to the rows you tagged yourself, with a breakdown by that column. | Free |
Take the in-market records from your database pull_my_database_in_market | Deliver the in-market records from your database: the identifiers you sent, the current mobile we hold, the topics each person is shopping, your own columns, and a list id on every row. Billed per record like any pull. | Spends records |
Send your in-market records to your own destination send_my_database_signals | Deliver the people in your database who are in market right now straight into your own S3 bucket or https endpoint, or as a CSV to the account email, instead of into a file somebody downloads. Billed per record, refused when the balance cannot cover it, and refunded in full if the delivery fails. | Spends records |
Standing feeds off your database list_database_feeds | Every feed running off your own databases: what fires it, what each row carries, where it lands, how often it runs, whether it is live, and what it last sent. | Free |
Read one standing feed get_database_feed | One feed in full, including whether it has passed a test delivery yet, which is what it needs before it can be switched on. | Free |
What a feed would send right now preview_database_feed | What a feed would send if it ran this minute, with a five row sample of the real file and what one run would cost. Nothing is created, delivered or charged. | Free |
Set up a feed off your database (paused) create_database_feed | When one of your own customers goes in market, calls in, or joins a category audience, that record comes back to you on your own schedule, with the appends you picked on it. Created paused, so nothing goes out until you have tested it and switched it on. | Free, creates a paused feed |
Send a free test delivery test_database_feed | Five real records to the real destination, free, marking nobody as already sent. This is what proves the destination works, and a feed cannot go live until it passes. | Free, sends a real test |
Switch a feed on start_database_feed | Put a feed live so it runs on its schedule. Refused until a test delivery has landed, because nothing should start a recurring delivery at a destination nobody has watched work. | Free, changes a feed |
Switch a feed off pause_database_feed | Stop a feed immediately. Records already delivered stay where they landed, and the test it passed still counts, so switching it back on needs no second test. | Free, changes a feed |
Change a standing feed update_database_feed | Rename it, re-time it, change how many records a run may send, change what each row carries, change the filters, or point it somewhere else. | Free, changes a feed |
Run a feed once, now run_database_feed_now | Run a standing feed outside its schedule and deliver for real. Billed per record like a scheduled run, and the people it sends are marked as already sent. | Spends records |
Things to ask it
Ask in your own words. These are just to show the shape of it.
“What can I target for solar? Show me the topics you have.”
Searches the topic catalog. Free, and a good first thing to ask.
“How many homeowners aged 55 to 75 in ZIPs 33710, 33711 and 33712 have a cell phone?”
Runs a count with a contactability filter and quotes the number that would actually ship.
“How many records have I used this month, and what is left?”
Reads your usage, your monthly limit, and your prepaid balance.
“Order me 5,000 of those homeowners with a cell phone.”
Places a real order and spends records, so your assistant will ask you first.
“Did that order finish? If it did, give me the download.”
Checks order status, then hands back a download command rather than the rows.
“Append phone numbers to these ten emails and tell me the match rate.”
Appends and reports counts. The numbers themselves stay out of the chat unless you ask for them.
What it will not do
- “What is the population of Tampa?” General knowledge. Nothing here should fire; this is not a question about the customer's data or an audience they can buy.
- “Write me a cold call script for solar.” Copywriting. No tool call, no records spent.
- “Delete my old orders and cancel my subscription.” Nothing on this surface deletes, cancels, or changes billing. The assistant should say so and point the person at their account settings.
What it costs
The connection is free and included with every plan. We do not charge for connecting, for how many assistants you connect, or for how many questions you ask.
What you spend through it is the work itself, at exactly the price it is everywhere else. Counts and estimates are free, so you can size anything you like before committing to it. An order spends records against your plan or your prepaid balance, the same records the same order would spend on our website or over the API, and it lands in the same usage log. Ask your assistant how many records you have used this month and it reads the figure off your account.
See pricing for what a record costs on each plan.
What happens to your data
Anything your assistant sees, it stores. That is true of every assistant, and it is their logs and their retention, not ours. So this connector is built to keep personal data out of the conversation in the first place.
- Ordering a list returns an order id and a download command. The records themselves never come back through the assistant. The file is emailed to your account.
- Appending phones returns match counts and which of your inputs matched. The phone numbers stay out unless you explicitly ask to see them, and even then at most 25 rows come back.
- Building an ad audience sends only SHA-256 hashes, and only to your own connected ad account.
- Looking up one person returns that one person, which is the product. There are modes that return a pass or fail, or hashes only, with no personal data at all.
Everything the connector does is the same thing our API does, billed and capped the same way, and written to the same usage log. Connecting an assistant grants it nothing you did not already have.
Our privacy policy covers what we collect, how it is stored, how long we keep it, and who to contact.
Support
Email support@talkdatatome.online and tell us which assistant you are using and what you asked it. If a tool failed, the message it gave you is the useful part.
Building something against the API directly instead? See the API documentation.