Twitter search Agent Skill

Give your AI agent the X Post Search through one prompt — it connects the official AgentBody skill and calls the real API automatically.

  • Search X Without An X Account
  • One Keyword, Ranked Results
  • Authors And Post Context
  • Paginated Result Sets

Install Skill

Read https://docs.agentbody.io/quickstart.md and help me safely connect, configure, and use AgentBody's APIs with the official AgentBody Skill in this agent environment.

Features

This X post search runs a keyword query across public posts, returning texts, authors, and engagement in one ranked, paginated feed — the discovery layer for research and monitoring workflows.

Search X Without An X Account

The query runs without signing in to X and without any X credentials. A free AgentBody account unlocks the request; you never hand over an X login to find public posts.

One Keyword, Ranked Results

Type what you are looking for — a phrase, a brand, a hashtag — and the search returns ranked public posts that match. It is post search proper: the texts, the authors, and the context, not just profile pages.

Authors And Post Context

Each result carries the post's URL, its text, the author's username, and available engagement numbers. That is enough to trace who said what and where, before committing to a deeper post lookup.

Paginated Result Sets

Results load page by page. When the response reports more matches, the next page follows with the returned cursor — so broad queries assemble completely instead of cutting off after the first screen.

How to use

Follow these six steps to use this X post search: pick a keyword, run the query, and page through the public results.

01

Create A Free Account

Create or sign in to your free AgentBody account before running the tool. The account unlocks the search request without connecting an X account or installing anything.

02

Choose Your Keyword

Pick the term that best describes what you are looking for — a phrase, a brand name, or an event. Public posts are searchable; protected accounts and deleted posts stay out of reach by design.

03

Enter The Query

Type the keyword into the input field on this page. Plain phrases work; there is no advanced syntax to learn on this page. One query returns one ranked result set of matching public posts.

Frequently asked questions

How to search for keywords on Twitter with this tool?

Create or sign in to a free AgentBody account, type the keyword into the input field, and click Run. The search returns ranked public posts matching the keyword — texts, authors, URLs, and engagement — with more pages available through the returned cursor.

Can I use Twitter search without an account?

Yes — without an X account. A free AgentBody account unlocks the request, but no X login or X credentials are involved at any point. The query runs against public posts and returns results directly in your browser.

Does it support Twitter advanced search operators?

No — this page runs plain keyword queries against public posts and returns structured results. It does not offer the operator set that advanced Twitter search uses — no from:, min_faves:, or date filters here. For those, combine this search with AgentBody's profile and post lookups.

Does the Twitter search cover historical posts?

The search returns what X publicly exposes for your query at request time. Very old or low-engagement posts can be missing from any search index, and protected or deleted posts are out of reach entirely — no search finds those.

Can I search one person's posts for a keyword?

Not on this page — it searches across public posts, not one account's timeline. For a specific user, AgentBody ships a separate profile posts operation; run that first, then match the keyword against the results locally.

How do I search X for a hashtag?

Type the hashtag term into the keyword field and run the search. Results include public posts matching the term; scan the texts and authors to find the conversation you are tracking.

Why did my X search return no results?

Either the phrase matches no public posts in the index, or the matching posts are protected or deleted. Try a broader phrase or fewer words. Input errors mean the query needs correcting; temporary failures can be retried.