api.gigsoul.com
https://api.gigsoul.com/analyze-marketing-trendsPaid verification
How it worksNo sponsored paid call yet.
Pay this endpoint once from your own wallet (Base USDC, up to $1.00) and we call it and record what came back. Your wallet pays the listed recipient directly; Agent Tools never holds funds. Sponsored checks prove delivery; they do not count as demand.
Quality grade
How grading works- ✓ Answers a real HTTP 402 challenge
- ✓ Publishes a /.well-known/x402 descriptor
- ✓ Payment address on record
- ✓ Settlement network declared
- ✓ Price declared
x402 readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 75.8/100), which weighs availability, payability and on-chain demand. How the two differ
| Valid payment requirements | 10/10 | Payment requirements carry a payee, a mainnet network and a price. |
| Live 402 challenge | 25/25 | Paid endpoint answers with an HTTP 402 challenge (139 ms). |
| x402 version | n/a | x402 version not observed yet. |
| Signed descriptor | n/a | No x402 standard defines a signed descriptor. |
| Uptime (30 days) | 15/15 | 32/32 probes succeeded over 30 days (100%). |
| Resource declaration | 10/10 | Declares 30 paid resource(s). |
| Verified identity | 5/10 | Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control. |
| Freshness + modern flags | 1/5 | not seen in a source for over 30 days; declares x402. |
| Security declaration | n/a | Payment is the access control for an x402 resource. |
Compared with peers
Against 10,060 reachable x402 APIs in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.
- Readiness
- Higher than 80% of peers
- This listing 88 · peer median 78
- Latency
- Faster than 72% of peers
- This listing 139 ms · peer median 205 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
- Freshness + modern flags −4
— Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days; declares x402.
Paid endpoints
30 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.
https://api.gigsoul.com/analyze-marketing-trends
Name the top 5 marketing trends for an industry or topic, with a short description of each. Use for trend briefings and idea generation. Based on model training knowledge, not a live lookup; figures are estimates. It may miss very recent shifts. For a full plan built on these, use generate-marketing
https://api.gigsoul.com/generate-marketing-strategy
Build a full go-to-market plan for a product: target audience, positioning, channels, and timeline. Use when starting from scratch or needing a whole plan. For only a tagline and value proposition, use generate-positioning-statement. For a 30-day posting schedule, use generate-content-calendar.
https://api.gigsoul.com/verify-deliverable-and-issue-acceptance-receipt
Verify a paid deliverable against its offer, original request, payment receipt, and acceptance rules. Returns ACCEPT/REJECT/REVIEW with stable reason codes, per-check booleans, content hashes, and an evidence packet. JSON-only checks: schema, required fields, freshness, source presence, receipt bind
https://api.gigsoul.com/webhook-lab-capture-simulate-replay
Disposable webhook test lab. capture: create a disposable HTTPS callback URL that records raw requests. retrieve: fetch captured requests. replay: send duplicate, out-of-order, delayed, malformed, or invalid-signature scenarios to your target URL. conformance: bounded webhook test battery with a mac
https://api.gigsoul.com/test-and-repair-automation-workflow
Validate and repair an n8n workflow JSON before production. static: deterministic plus model checks of nodes, connections, credentials, expressions, reachability. simulated: synthetic dry run with safe fixtures. repair: minimal RFC 6902 JSON Patch plus a replay fixture, re-validated in-worker. Retur
https://api.gigsoul.com/analyze-competitors
Map a market's competitors: names, strengths, weaknesses, and how each is positioned. Use for landscape and positioning questions ('who else does X and how do they differ'). Pricing is not covered; for plan tiers and price comparison use research-competitor-pricing. Based on model training knowledge
https://api.gigsoul.com/analyze-seo-keywords
Suggest the top 10 SEO keywords for a topic with estimated relative search volume and difficulty. Use for early keyword ideation and content planning. Based on model training knowledge, not a live lookup; figures are estimates. Not live keyword-tool data; validate volumes in an SEO tool before commi
https://api.gigsoul.com/generate-linkedin-post
Write one LinkedIn post on a topic: post text, hashtags, and an opening hook. Use for a single original post. To adapt an existing article for LinkedIn and other channels at once, use repurpose-long-form. To score a draft before posting, use predict-viral-potential.
https://api.gigsoul.com/generate-cold-email
Write a first-touch cold email for a product and audience: subject line, preview text, and a 100-150 word body. Use for the opening message. For the follow-ups after no reply, use generate-follow-up-sequence. To check spam risk before sending, use check-email-deliverability.
https://api.gigsoul.com/research-prospect
Research a sales prospect company: company profile, decision-maker role profile (role-level, not a named person), likely pain points, and an outreach angle. Use before writing outreach; then use generate-cold-email. Based on model training knowledge, not a live lookup; figures are estimates.
https://api.gigsoul.com/summarize-document
Condense a document or article into what it says: main argument, key findings, and supporting evidence. Use when you need a faithful digest with no opinion added. For judgment on top of the content (insights, gaps, recommended actions), use analyze-document. To turn an article into social posts, use
https://api.gigsoul.com/analyze-document
Evaluate a document or article and say what to do about it: a short summary plus key insights, weaknesses or gaps, and concrete recommendations. Use when you need judgment or next steps. For a neutral digest only, use summarize-document (cheaper). For customer complaints inside a text, use extract-p
https://api.gigsoul.com/thread-from-article
Turn one article into an X/Twitter thread of 5-10 posts. Use when X is the only target. For LinkedIn, email, and blog versions at once, use repurpose-long-form. URLs are not fetched; paste the text.
https://api.gigsoul.com/repurpose-long-form
Repurpose one long piece for several channels at once: a LinkedIn post, an X thread, an email draft, and a blog intro. Use when you need all four. For an X thread only, use thread-from-article (cheaper). URLs are not fetched; paste the text.
https://api.gigsoul.com/generate-show-notes
Write podcast show notes from a transcript or outline: episode summary, key timestamps, guest bio, and links. Timestamps and links come only from the input; supply a transcript with times for accurate timestamps. URLs are not fetched; paste the text.
https://api.gigsoul.com/extract-pain-points
Pull the top 5 customer pain points out of text you supply (reviews, interview notes, support tickets, forum threads), each with severity and a suggested fix. Use when you have raw customer voice. For overall tone and emotion, use analyze-sentiment. For review trends over time, use analyze-review-ve
https://api.gigsoul.com/analyze-sentiment
Classify the overall sentiment of a text and name its key themes and emotional triggers. Use for 'how do people feel about this'. For specific problems to fix, use extract-pain-points. For review momentum over time, use analyze-review-velocity.
https://api.gigsoul.com/research-competitor-pricing
Compare competitor pricing in a product category: competitor names, plan tiers and price points, and a value-for-money comparison. Use for pricing and packaging decisions. For strengths, weaknesses, and positioning, use analyze-competitors. Based on model training knowledge, not a live lookup; figur
https://api.gigsoul.com/generate-positioning-statement
Write positioning for one product: tagline, value proposition, and differentiation. Use for a single positioning block. For a full plan with channels and timeline, use generate-marketing-strategy. For competitor research first, use analyze-competitors.
https://api.gigsoul.com/generate-follow-up-sequence
Write a 3-email follow-up sequence (subjects, timing, and body) for prospects who did not reply to a first email. For the first-touch email, use generate-cold-email.
https://api.gigsoul.com/generate-webinar-invite
Write webinar invitation copy: two invite emails and a landing-page blurb. Use when promoting a scheduled webinar or live event.
https://api.gigsoul.com/generate-case-study-questions
Write 10 open-ended discovery questions, grouped by category, for interviewing a customer for a full written case study (problem, solution, results). For short quotable praise, use generate-testimonial-questions.
https://api.gigsoul.com/generate-testimonial-questions
Write 8 short questions that draw out quotable customer testimonials. Use when you need quotes, not a long story. For a full case-study interview, use generate-case-study-questions.
https://api.gigsoul.com/analyze-review-velocity
Judge review momentum from review data you supply (dates, ratings, text): velocity score, sentiment trend, and response recommendations. Use for 'are reviews speeding up or slowing down, and how should we respond'. You must include the reviews; it does not fetch from G2, Capterra, or app stores. For
https://api.gigsoul.com/generate-content-calendar
Plan a 30-day content calendar: daily themes, post types, and a posting schedule. Use for planning a month of content. For the overall strategy behind it, use generate-marketing-strategy. For the posts themselves, use generate-linkedin-post or repurpose-long-form.
https://api.gigsoul.com/predict-viral-potential
Score a draft post before publishing: a virality score broken down by emotion, specificity, novelty, and shareability, plus the best-fit platform. A heuristic prediction, not a reach forecast. For landing-page copy use score-landing-page; to generate test variants use generate-ab-test-variants.
https://api.gigsoul.com/generate-ab-test-variants
Create 3 A/B test variants of existing marketing copy, one variable changed per variant, each with a hypothesis, plus a test plan (primary metric, sample size, duration). Tone stays close to the source. Use when you already have copy to test. To score copy without variants, use score-landing-page or
https://api.gigsoul.com/analyze-email-deliverability
Full deliverability audit of email copy: 0-100 score, every flagged phrase with its reason, subject-line risk, concrete rewrites, and SPF/DKIM/DMARC reminders. Use when a draft failed or warned in check-email-deliverability, or before an important send. For a quick pass/fail on many emails, use chec
https://api.gigsoul.com/check-email-deliverability
Fast, cheap spam-risk gate for one email: pass/warn/fail, a 0-100 score, and up to 3 flagged phrases. Use for a go/no-go before sending or for bulk screening of many drafts. No rewrites. For a full audit with reasons, subject-line risk, and rewritten copy, use analyze-email-deliverability. Content s
https://api.gigsoul.com/score-landing-page
Score landing-page copy for conversion: 0-100 with a 5-part breakdown (headline, value proposition, social proof, CTA, friction), the top 3 issues, and 3 quick-win rewrites. Use for a page's text. URLs are not fetched; paste the text. For social posts, use predict-viral-potential.
How to call
curl -sS -i -X POST https://api.gigsoul.com/analyze-marketing-trends # expect HTTP 402 Payment Required (about 0.05 USDC/call)
Listed in
Directories this entry was found in.