{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"scaleserp","slug":"scaleserp","name":"ScaleSerp","type":"api","url":"https://scaleserp.com","page_url":"https://unfragile.ai/scaleserp","categories":["llm-apis"],"tags":[],"pricing":{"model":"free","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"scaleserp__cap_0","uri":"capability://search.retrieval.real.time.google.serp.parsing.with.multi.format.result.extraction","name":"real-time google serp parsing with multi-format result extraction","description":"Executes queries against Google search engines and returns parsed organic results, ads, knowledge graph, shopping results, news, and images in structured JSON format. Uses full in-memory browser rendering to capture dynamic content without manual parsing rules, then automatically extracts and structures SERP components (titles, descriptions, URLs, rankings, rich snippets) into machine-readable format. Processes results synchronously with claimed zero-queue latency, returning complete SERP data in a single API response.","intents":["I need to programmatically fetch Google search results for a given query and extract structured data about organic rankings, ads, and knowledge panels","I want to monitor SERP changes for specific keywords across different geographies and device types to track SEO performance","I need to build a search intelligence tool that aggregates Google results without maintaining my own scraping infrastructure","I want to compare search results across multiple locations and devices to understand localization and personalization effects"],"best_for":["SEO agencies and tools building rank tracking, competitive analysis, and keyword research platforms","Data scientists building search intelligence datasets for ML training","Enterprise teams needing reliable, quota-managed access to SERP data without infrastructure overhead","Developers building search-augmented LLM applications requiring fresh, structured search context"],"limitations":["Query length limits and result depth/pagination constraints are undocumented — maximum queryable results per search unknown","Latency profile is claimed as 'real-time' but actual P50/P95/P99 response times are not published","Response schema and field definitions are not provided in documentation — integration requires reverse-engineering from examples","No streaming response support documented — all results returned in single synchronous response, limiting real-time result streaming use cases","Geolocation targeting is limited to country, city, state, and postal code granularity — cannot target specific ISPs or network segments"],"requires":["API key (authentication mechanism format undocumented)","Active paid plan or free tier account (125 searches/month free)","HTTP client library (Node.js, Python, PHP, or cURL)","Familiarity with REST API patterns and JSON parsing"],"input_types":["text (search query string)","enum (country/location code for geolocation targeting)","enum (device type: desktop, mobile, tablet)","enum (search type: organic, shopping, news, images, video, scholar, products, trends, places)"],"output_types":["JSON (structured SERP data with organic results, ads, knowledge graph, shopping results, news articles, image results, rich snippets)"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"scaleserp__cap_1","uri":"capability://search.retrieval.geolocation.targeted.search.result.retrieval.with.device.type.simulation","name":"geolocation-targeted search result retrieval with device type simulation","description":"Executes searches from specific geographic locations (country, city, state, postal code level) and simulates different device types (desktop, mobile, tablet) to capture location-specific and device-specific SERP variations. Internally routes requests through location-specific infrastructure or proxy networks to return results as they would appear to users in that geography and on that device type. Supports dynamic location discovery via Locations API endpoint that returns all supported geographic targets.","intents":["I need to check how my website ranks for a keyword in different countries and cities to understand geographic SEO performance","I want to see how search results differ between desktop and mobile devices to optimize for mobile-first indexing","I need to test whether my local SEO efforts are working by checking rankings from specific city/state locations","I want to understand how Google personalizes results by comparing searches from different geographic regions"],"best_for":["SEO professionals managing multi-location or international campaigns","Local business owners tracking rankings across service areas","Mobile-first product teams validating mobile SERP optimization","International SaaS companies monitoring localized search visibility"],"limitations":["Supported locations are limited to predefined geographic targets — cannot target arbitrary IP addresses or custom network segments","Location granularity maxes out at postal code level — cannot target specific neighborhoods or micro-locations","Device simulation is limited to three types (desktop, mobile, tablet) — cannot simulate specific browser versions, OS versions, or user agents","No documentation on how location targeting is implemented (proxy routing, local infrastructure, or other mechanism) — unclear if results are truly localized or approximated"],"requires":["Valid location code from Locations API (must query Locations endpoint first to discover supported targets)","Device type parameter (desktop, mobile, or tablet)","API key with active subscription"],"input_types":["enum (country code or city/state/postal code identifier)","enum (device type: desktop, mobile, tablet)","text (search query)"],"output_types":["JSON (SERP results as they appear in the specified location and device context)"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"scaleserp__cap_10","uri":"capability://data.processing.analysis.news.results.and.article.extraction.from.serp.results","name":"news results and article extraction from serp results","description":"Extracts Google News results and news articles from SERP results, including article titles, publication dates, source information, and article snippets. Parses the Google News carousel and news section layout to structure article data into machine-readable format. Supports extraction of news results for both news-specific queries and general queries that include news coverage.","intents":["I want to monitor news coverage for my brand or industry keywords to track media mentions","I need to extract news articles from Google News results for content aggregation or analysis","I want to analyze news coverage trends for specific keywords or entities over time","I need to identify which news sources are covering specific topics for media monitoring"],"best_for":["Brand monitoring and PR teams tracking media mentions and news coverage","News aggregation platforms collecting articles from Google News results","Content teams analyzing news coverage and media trends for specific topics","Researchers studying news coverage and media bias across sources"],"limitations":["News results availability is query-dependent — not all queries return Google News results","Article snippets are truncated — full article text is not extracted, only Google's displayed snippet","Publication date accuracy may vary — Google's date parsing may not match actual article publication dates","No article content extraction — only metadata (title, date, source) and snippet are extracted, not full article text"],"requires":["API key with active subscription","Search query that returns Google News results"],"input_types":["text (news search query)"],"output_types":["JSON (news articles with titles, publication dates, source information, snippets)"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"scaleserp__cap_11","uri":"capability://data.processing.analysis.image.results.extraction.with.image.urls.and.metadata","name":"image results extraction with image urls and metadata","description":"Extracts Google Images results from SERP results, including image URLs, alt text, source URLs, and image dimensions. Parses the Google Images grid layout to structure image data into machine-readable format. Supports extraction of image metadata for image search analysis and visual content monitoring.","intents":["I want to monitor image search results for my brand or products to track visual content visibility","I need to extract image URLs and source information from Google Images results for content analysis","I want to analyze which images rank for specific keywords to understand visual search intent","I need to identify unauthorized use of my images by extracting image results and source URLs"],"best_for":["Visual content teams monitoring image search visibility for brands or products","Image licensing and copyright teams tracking unauthorized image use","Content teams analyzing visual search intent and image ranking factors","Researchers studying image search results and visual content trends"],"limitations":["Image results availability is query-dependent — not all queries return Google Images results","Image URLs may be proxied through Google — direct source URLs may not be accessible","Image metadata (dimensions, file size) is limited to what Google displays — full image metadata not available","No image content analysis — only URLs and metadata are extracted, not image content or visual features"],"requires":["API key with active subscription","Search query that returns Google Images results"],"input_types":["text (image search query)"],"output_types":["JSON (image results with URLs, alt text, source URLs, dimensions)"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"scaleserp__cap_2","uri":"capability://automation.workflow.batch.search.queueing.and.asynchronous.execution.with.quota.management","name":"batch search queueing and asynchronous execution with quota management","description":"Accepts up to 15,000 search requests in a single batch operation and enqueues them for asynchronous execution. Batches are processed according to plan-specific concurrency limits (up to 15,000 parallel searches for higher tiers) and are tracked separately from real-time API quota. Failed batch searches do not consume quota, reducing cost for unreliable or exploratory batch operations. Batch operations are limited to 10,000 total batches per billing period.","intents":["I need to run 5,000+ keyword rank checks overnight without hitting rate limits or blocking my real-time API traffic","I want to bulk-check rankings for my entire keyword list monthly without paying for failed requests","I need to process large-scale SERP data collection jobs (e.g., competitive analysis across 10,000 keywords) without managing my own queue infrastructure","I want to separate batch/background jobs from real-time search requests to avoid contention"],"best_for":["SEO agencies running nightly rank tracking jobs for multiple clients","Data teams collecting large SERP datasets for analysis or ML training","Developers building background job systems that need reliable, quota-aware batch processing","Teams with bursty search workloads that need to smooth demand across time"],"limitations":["Batch execution timing is undocumented — no SLA for when batches will be processed or completed","No callback/webhook mechanism documented — polling for batch completion status is likely required","Batch limit of 10,000 per billing period means large-scale operations must be split across multiple periods or use real-time API","Batch scheduling options are undocumented — cannot specify execution time, priority, or dependencies between batch jobs","No batch result streaming — entire batch results must be retrieved in a single response, limiting memory efficiency for very large batches"],"requires":["API key with active paid subscription (batches not available on free tier, likely)","Array of up to 15,000 search request objects with query, location, and device parameters","Mechanism to poll or retrieve batch results (webhook support unknown)"],"input_types":["JSON array (batch of search request objects, each containing query, location, device type)"],"output_types":["JSON (array of SERP results corresponding to input batch, or batch job ID for polling)"],"categories":["automation-workflow","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"scaleserp__cap_3","uri":"capability://search.retrieval.multi.serp.type.result.aggregation.in.single.request","name":"multi-serp-type result aggregation in single request","description":"Supports querying multiple Google search result types (organic, shopping, news, images, video, scholar, products, trends, places/maps, reviews) in a single API request and returns all result types in a unified JSON response. Internally routes the query to multiple Google search verticals and aggregates parsed results from each vertical into a single structured response, eliminating the need for separate API calls per result type.","intents":["I want to get organic results, shopping results, and news articles for a query in a single API call to reduce latency and request count","I need to build a universal search tool that shows results from multiple Google verticals (organic, images, news, shopping) in one view","I want to analyze whether a keyword has shopping results, news coverage, and academic papers (scholar) to understand search intent","I need to check if a brand appears in Google Places/Maps results alongside organic results for local SEO analysis"],"best_for":["Search intelligence platforms aggregating results from multiple Google verticals","Content teams analyzing search intent by examining result type diversity","E-commerce platforms checking product visibility across organic and shopping results","Researchers collecting comprehensive SERP data across multiple result types"],"limitations":["Result type availability per query is undocumented — some queries may not return all result types (e.g., shopping results for non-commercial queries)","No control over which result types are returned — cannot selectively request only specific verticals to reduce response size","Response schema for each result type is undocumented — integration requires reverse-engineering from examples","Aggregation logic is opaque — unclear how results are ranked or ordered when multiple types are present in single response"],"requires":["API key with active subscription","Search query parameter","Optional: result type filter (if supported, undocumented)"],"input_types":["text (search query)","enum (result types: organic, shopping, news, images, video, scholar, products, trends, places, reviews)"],"output_types":["JSON (unified response containing results from all requested/available SERP types)"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"scaleserp__cap_4","uri":"capability://automation.workflow.tiered.quota.management.with.overage.based.pricing.and.failed.request.exemption","name":"tiered quota management with overage-based pricing and failed-request exemption","description":"Implements a tiered monthly quota system (125 searches/month free tier up to 5,000,000/month enterprise) with per-search overage pricing that decreases as volume increases ($0.038/search for 1K tier down to $0.001999/search for 5M tier). Failed API requests do not consume quota, reducing cost for unreliable operations. Quota resets monthly and can be purchased annually at 20% discount. Overage charges are applied automatically when monthly quota is exceeded, with no hard limits or request blocking.","intents":["I need to understand my search API costs and predict monthly spend based on my query volume","I want to optimize costs by choosing the right tier for my expected monthly search volume","I need to avoid surprise bills by understanding how overage pricing works and when it applies","I want to take advantage of annual billing discounts to reduce my API costs"],"best_for":["Startups and small teams with predictable, low-volume search needs (under 10K searches/month)","Enterprises with high-volume, consistent search workloads (1M+ searches/month) that can negotiate custom pricing","Cost-conscious teams that want to avoid per-token pricing models and prefer predictable monthly costs","Teams with variable search volume that want to avoid hard rate limits and pay only for what they use"],"limitations":["Overage pricing is per-search, not per-token, making it difficult to predict costs for variable query complexity","No hard rate limits documented — unclear if requests are rejected or queued when quota is exceeded","Free tier limitations are undocumented — unclear if free tier has feature restrictions (e.g., no batch API, no certain result types)","No usage alerts or quota monitoring API documented — developers must manually track usage to avoid surprise overages","Annual billing discount (20%) is fixed — no volume-based discounts beyond the tiered pricing structure"],"requires":["Active account with payment method on file (Visa, Mastercard, American Express via Stripe)","Selection of appropriate tier based on expected monthly search volume","Optional: annual billing preference to receive 20% discount"],"input_types":["enum (billing tier: free, 1K, 10K, 50K, 250K, 1M, 5M, or custom enterprise)"],"output_types":["JSON (billing summary, quota remaining, overage charges, usage metrics)"],"categories":["automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"scaleserp__cap_5","uri":"capability://search.retrieval.dynamic.location.discovery.and.validation.api","name":"dynamic location discovery and validation api","description":"Provides a dedicated Locations API endpoint that returns all supported geographic locations for search targeting, queryable by country, city, state, or postal code. Developers can programmatically discover valid location parameters before executing searches, eliminating the need to hardcode location codes or maintain external location reference lists. Location data is updated dynamically as new locations are added to the platform.","intents":["I need to discover all supported locations for my target markets without hardcoding location codes","I want to validate user-provided location inputs against supported locations before executing searches","I need to build a location picker UI that shows all available search locations dynamically","I want to ensure my location-targeted searches use valid location codes to avoid API errors"],"best_for":["Developers building location-aware search tools that need to support user-selected locations","Teams managing international campaigns across multiple markets and needing dynamic location discovery","Applications requiring location validation before executing geo-targeted searches","Platforms that need to stay synchronized with newly added location support"],"limitations":["Location granularity is limited to postal code level — cannot discover or target sub-postal-code locations","No hierarchical location data documented — unclear if API returns parent-child relationships (e.g., city within state within country)","Query performance for large location lists is undocumented — unclear if pagination or filtering is supported","Location update frequency is undocumented — unclear how quickly new locations appear in the API after being added to the platform"],"requires":["API key with active subscription","Optional: location query filter (country, city, state, or postal code)"],"input_types":["text (optional location query string for filtering)"],"output_types":["JSON (array of supported locations with location codes, names, and hierarchy information)"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"scaleserp__cap_6","uri":"capability://data.processing.analysis.automatic.serp.parsing.without.manual.rule.configuration","name":"automatic serp parsing without manual rule configuration","description":"Automatically extracts and structures SERP components (titles, descriptions, URLs, rankings, rich snippets, knowledge panels, ads, shopping results) from Google search results without requiring developers to write custom parsing rules, CSS selectors, or regex patterns. Uses full in-memory browser rendering to capture dynamic content and applies machine learning or heuristic-based extraction to identify and structure SERP elements automatically. Handles SERP layout variations across different query types and geographies without rule updates.","intents":["I want to extract structured SERP data without writing and maintaining custom parsing rules or CSS selectors","I need to handle SERP layout changes automatically without updating my parsing logic every time Google changes the results page","I want to extract rich snippets, knowledge panels, and other complex SERP elements that are difficult to parse with regex or CSS selectors","I need to parse SERP results across multiple geographies and query types without maintaining separate parsing rules for each variant"],"best_for":["Teams building SERP analysis tools that need to handle SERP variations without constant rule maintenance","Developers who want to avoid the complexity of maintaining Selenium/Puppeteer scraping scripts with custom parsing logic","Organizations that need to extract complex SERP elements (knowledge panels, rich snippets, featured snippets) reliably","Platforms that need to support multiple languages and geographies without duplicating parsing logic"],"limitations":["Parsing logic is opaque — no documentation on how extraction rules are applied or how conflicts are resolved","No control over parsing behavior — cannot customize which SERP elements are extracted or how they are structured","Extraction accuracy is undocumented — no published metrics on false positive/negative rates for different SERP element types","No fallback mechanism documented — unclear how the API handles SERP layouts it cannot parse automatically"],"requires":["API key with active subscription","Search query and location/device parameters"],"input_types":["text (search query)"],"output_types":["JSON (automatically parsed and structured SERP data with titles, descriptions, URLs, rankings, snippets, knowledge panels)"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"scaleserp__cap_7","uri":"capability://code.generation.editing.code.generation.for.api.requests.across.multiple.languages","name":"code generation for api requests across multiple languages","description":"Provides an interactive API Playground that auto-generates request code samples in Node.js, Python, PHP, and cURL based on parameter selections. Developers configure search parameters (query, location, device type, result type) in the UI and the playground dynamically generates executable code snippets in their language of choice. Generated code includes proper authentication, error handling, and response parsing patterns.","intents":["I want to quickly generate working code samples for my preferred language without manually writing API request boilerplate","I need to see how to structure API requests and parse responses before integrating ScaleSerp into my application","I want to test different parameter combinations and see the generated code change in real-time","I need to copy-paste working code samples into my project to accelerate integration"],"best_for":["Developers new to the ScaleSerp API who want to get started quickly with working code samples","Teams supporting multiple programming languages that need consistent code generation across languages","Rapid prototyping and proof-of-concept work where developers want to minimize boilerplate writing","Documentation and onboarding — code generation serves as interactive API documentation"],"limitations":["Generated code quality is undocumented — unclear if generated code follows best practices for error handling, retries, or rate limiting","No customization of generated code — developers cannot specify code style, dependencies, or architectural patterns","Limited language support — only Node.js, Python, PHP, and cURL are supported; no Go, Rust, Java, or other languages","Generated code may require manual adjustments — unclear if generated code is production-ready or requires modification"],"requires":["Web browser access to API Playground","No API key required for code generation (only for executing generated code)"],"input_types":["UI form inputs (query, location, device type, result type, other parameters)"],"output_types":["text (executable code in Node.js, Python, PHP, or cURL format)"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"scaleserp__cap_8","uri":"capability://data.processing.analysis.knowledge.graph.and.rich.snippet.extraction.from.serp.results","name":"knowledge graph and rich snippet extraction from serp results","description":"Automatically extracts and structures knowledge graph data (entity information, properties, relationships) and rich snippets (featured snippets, answer boxes, People Also Ask sections) from Google search results. Parses complex SERP elements like knowledge panels, entity cards, and structured data markup into machine-readable JSON format, enabling applications to access high-value SERP real estate without manual DOM parsing.","intents":["I want to extract knowledge graph data (entity properties, relationships) from SERP results for knowledge base enrichment","I need to monitor featured snippets and answer boxes for my target keywords to understand search intent","I want to analyze People Also Ask sections to discover related search queries and content gaps","I need to extract structured entity information from knowledge panels for competitive analysis"],"best_for":["Content teams analyzing featured snippet opportunities and search intent","Knowledge base and entity management platforms enriching data from SERP results","SEO agencies tracking featured snippet ownership and answer box visibility","Researchers studying knowledge graph structure and entity relationships"],"limitations":["Knowledge graph availability is query-dependent — not all queries return knowledge graph data","Rich snippet structure varies by query type — no standardized schema for different snippet types (featured, answer box, People Also Ask)","Extraction accuracy for complex snippets is undocumented — unclear how nested or multi-part snippets are parsed","No control over which rich snippet types are extracted — all available snippets are returned without filtering options"],"requires":["API key with active subscription","Search query that returns knowledge graph or rich snippet data"],"input_types":["text (search query)"],"output_types":["JSON (knowledge graph data, featured snippets, answer boxes, People Also Ask sections, entity cards)"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"scaleserp__cap_9","uri":"capability://data.processing.analysis.shopping.results.and.product.listing.extraction.with.pricing.data","name":"shopping results and product listing extraction with pricing data","description":"Extracts Google Shopping results and product listings from SERP results, including product titles, prices, merchant information, ratings, and product images. Parses the Google Shopping carousel and product grid layout to structure product data into machine-readable format. Supports extraction of pricing data across multiple merchants for the same product, enabling price comparison and competitive analysis.","intents":["I want to monitor product prices and merchant listings for my products on Google Shopping","I need to extract competitor product listings and pricing from Google Shopping results for competitive analysis","I want to build a price comparison tool that aggregates product listings from Google Shopping","I need to track which merchants are showing products in Google Shopping results and their pricing"],"best_for":["E-commerce teams monitoring product visibility and pricing on Google Shopping","Price comparison platforms aggregating product listings and pricing from Google Shopping","Competitive intelligence teams tracking competitor product listings and pricing strategies","Retailers optimizing product feed and pricing for Google Shopping visibility"],"limitations":["Shopping results availability is query-dependent — not all queries return Google Shopping results","Pricing data may be incomplete or outdated — no guarantee that extracted prices match current merchant prices","Merchant information extraction is limited to what Google displays — cannot access full merchant catalogs or inventory","No product image download or processing — images are returned as URLs only, requiring separate image processing"],"requires":["API key with active subscription","Search query that returns Google Shopping results"],"input_types":["text (product search query)"],"output_types":["JSON (product listings with titles, prices, merchant information, ratings, image URLs)"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"scaleserp__headline","uri":"capability://search.retrieval.google.search.results.api","name":"google search results api","description":"A fast and affordable API for retrieving and parsing Google search results, including organic results, ads, and knowledge graph data, with geolocation targeting and device simulation.","intents":["best Google search results API","Google search API for location-based data","affordable API for Google search results","API for parsing Google search results","Google search results API with device simulation"],"best_for":["developers needing search data","businesses targeting specific locations"],"limitations":[],"requires":["API key"],"input_types":["search queries"],"output_types":["parsed search results"],"categories":["search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":58,"verified":false,"data_access_risk":"high","permissions":["API key (authentication mechanism format undocumented)","Active paid plan or free tier account (125 searches/month free)","HTTP client library (Node.js, Python, PHP, or cURL)","Familiarity with REST API patterns and JSON parsing","Valid location code from Locations API (must query Locations endpoint first to discover supported targets)","Device type parameter (desktop, mobile, or tablet)","API key with active subscription","Search query that returns Google News results","Search query that returns Google Images results","API key with active paid subscription (batches not available on free tier, likely)"],"failure_modes":["Query length limits and result depth/pagination constraints are undocumented — maximum queryable results per search unknown","Latency profile is claimed as 'real-time' but actual P50/P95/P99 response times are not published","Response schema and field definitions are not provided in documentation — integration requires reverse-engineering from examples","No streaming response support documented — all results returned in single synchronous response, limiting real-time result streaming use cases","Geolocation targeting is limited to country, city, state, and postal code granularity — cannot target specific ISPs or network segments","Supported locations are limited to predefined geographic targets — cannot target arbitrary IP addresses or custom network segments","Location granularity maxes out at postal code level — cannot target specific neighborhoods or micro-locations","Device simulation is limited to three types (desktop, mobile, tablet) — cannot simulate specific browser versions, OS versions, or user agents","No documentation on how location targeting is implemented (proxy routing, local infrastructure, or other mechanism) — unclear if results are truly localized or approximated","News results availability is query-dependent — not all queries return Google News results","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.7,"quality":0.9,"ecosystem":0.15000000000000002,"match_graph":0.25,"freshness":0.75,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.1,"match_graph":0.28,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:25.061Z","last_scraped_at":null,"last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=scaleserp","compare_url":"https://unfragile.ai/compare?artifact=scaleserp"}},"signature":"c2Iv2GEuigc731efbdVlLFhVfmke8JL8tWSd3p+Tlp7evuuJ7N1VJ7kjq20sPapmXJ9sa/UZ4j0T6OdlYtYWAA==","signedAt":"2026-06-23T03:31:20.780Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/scaleserp","artifact":"https://unfragile.ai/scaleserp","verify":"https://unfragile.ai/api/v1/verify?slug=scaleserp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}