Aries — Daily horoscope
…
Love
…
Work
…
Energy
…
Publish the complete daily, weekly or monthly horoscope on your own site, under your own template, in fifteen languages: for free. One rule makes it work for both of us: the full text carries a canonical tag pointing back at the source.
This is the exact HTML the API returns. There is no class attribute, no style attribute, no div, no color and no font in it: only the semantic elements your CMS already styles. Your stylesheet wins because ours never enters the page. The same article is also available as markdown, plain text or schema.org JSON.
GET /api/v1/daily?full=1&format=html<article>
<h1>Aries — Daily horoscope</h1>
<section>
<p>…</p>
</section>
<section>
<h2>Love</h2>
<p>…</p>
</section>
<section>
<h2>Work</h2>
<p>…</p>
</section>
<section>
<h2>Energy</h2>
<p>…</p>
</section>
<p><a href="https://sigastra.com/daily-horoscope">Powered by Sigastra</a></p>
</article># Aries — Daily horoscope … ## Love … ## Work … ## Energy … [Powered by Sigastra](https://sigastra.com/daily-horoscope)
Nothing below was re-authored. Each panel is the identical HTML above, dropped into a different stylesheet: a broadsheet, a modern magazine and a minimal blog. That is the whole point of shipping unstyled content: it becomes yours on arrival.
…
…
…
…
…
…
…
…
…
…
…
…
Every item in the feed carries a hero image, rendered server-side from vector art: no stock photos, no licensing trail. A horoscope without a picture loses its slot in your card grid to the twelve stories that have one, and no desk is going to source art for twelve posts a day.
hero 1200×630 · wide 1600×900 · card 800×800 — dark and light, because your article template is probably white
Four formats over the same content. MRSS and schema.org Article are the two a publishing pipeline usually already speaks; JSON and RSS remain for consumers built on them.
| Format | URL | What it carries |
|---|---|---|
| MRSS | /feed/daily/mrss?lang=en | Full text in content:encoded, hero image, Dublin Core, canonical as the item link. Needs your site as Referer, or your key. |
| Article JSON | /feed/daily/article?lang=en | schema.org Article objects with the full text. Needs your site as Referer, or your key. |
| JSON | /feed/daily/json?lang=en | Teasers with a link to each sign, for feed readers and simple templates. |
| RSS 2.0 | /feed/daily/rss?lang=en | Plain RSS with teasers and links, for feed readers. |
daily · weekly · monthly · moon · cosmic. Swap the segment, and add &sign= for one sign.
Pick MRSS if your CMS ingests XML, or the schema.org Article JSON if it ingests JSON. Add ?lang= for the language and ?sign= for a single sign; leave it off for all twelve.
headline, dek, byline, published, category, tags, wordCount and image are all separate fields. You do not have to parse our markup to fill your own.
The body is unstyled semantic HTML (or markdown, if you prefer). Drop it into your article component and your own CSS takes over.
Publishing the full text means adding the supplied canonical tag to that page’s head, and rendering the “Powered by Sigastra” link with the content. Those two lines are the entire price.
The same article in a neutral template, with the canonical, the credit link and the schema.org Article in the head. View-source is the documentation.
One download with a real response in every format: JSON envelope, unstyled HTML, markdown, MRSS, schema.org Article: plus a hero image in both themes and a README with the field map. Enough for your team to build the importer before talking to us.
Download the sample kitYou get a finished editorial product: twelve signs, written to the day’s real sky, updated every morning without anyone on your side touching it. We get one visible link and, for full text, a canonical tag. No money moves in either direction and there is no contract to sign. The four points below are the essentials; the complete terms are at the bottom of this page and apply to syndication as well.
An excerpt (a card, a sidebar, a few lines) needs the visible “Powered by Sigastra” link and nothing else: no canonical, no forms, no notification.
If you publish the whole horoscope, add the canonical tag to that page’s <head>. It is one line, we hand you the exact string, and it is the difference between syndication and a duplicate-content problem for both sites.
Visible on the page that shows the content and readable without a login. Next to the content is best; the check accepts it anywhere on that page, but not hidden and not inside our frame.
An importer or a nightly job calls from your server, so it sends your page address as the Referer or, once your site has passed the check, the free key. Storing, translating, apps and everything else are covered by the full terms below.
Put this in the <head> of the page carrying the full text. The API returns the correct URL for every sign, language and period in attribution.canonicalTag: copy it from the payload rather than building it yourself, so a language or slug change on our side never leaves you pointing at a redirect.
<link rel="canonical" href="https://sigastra.com/daily-horoscope">
attribution.canonicalTag · attribution.canonicalRequired = true
A complete, self-contained block: the twelve horoscopes, the credit link and a comment showing the canonical tag to add. Paste it into a CMS that accepts HTML.
<!-- Add this to the <head> of THIS page: -->
<!-- <link rel="canonical" href="https://sigastra.com/daily-horoscope"> -->
<section class="sigastra-daily">
<article>
<h3>Aries — Daily horoscope</h3>
<p>…</p>
</article>
<article>
<h3>Taurus — Daily horoscope</h3>
<p>…</p>
</article>
<article>
<h3>Gemini — Daily horoscope</h3>
<p>…</p>
</article>
<article>
<h3>Cancer — Daily horoscope</h3>
<p>…</p>
</article>
<article>
<h3>Leo — Daily horoscope</h3>
<p>…</p>
</article>
<article>
<h3>Virgo — Daily horoscope</h3>
<p>…</p>
</article>
<article>
<h3>Libra — Daily horoscope</h3>
<p>…</p>
</article>
<article>
<h3>Scorpio — Daily horoscope</h3>
<p>…</p>
</article>
<article>
<h3>Sagittarius — Daily horoscope</h3>
<p>…</p>
</article>
<article>
<h3>Capricorn — Daily horoscope</h3>
<p>…</p>
</article>
<article>
<h3>Aquarius — Daily horoscope</h3>
<p>…</p>
</article>
<article>
<h3>Pisces — Daily horoscope</h3>
<p>…</p>
</article>
<p><a href="https://sigastra.com/daily-horoscope">Powered by Sigastra</a></p>
</section>For anything beyond a one-off paste (a nightly job, a template) call the API with full=1 and render it yourself. Same content, same conditions.
curl -s "https://sigastra.com/api/v1/daily?lang=en&full=1"API →
Nothing. There is no fee and no contract; a server-side call names your site with its page address or, once the link is checked, a free key. The conditions are a visible credit link and, for full text, a canonical tag.
Because the full text on your page and the full text on ours are identical, and without a canonical a search engine has to guess which is the original. The tag removes the guess. It also protects you: your page is not competing with ours.
Not with the canonical in place. That is exactly what it is for. You keep a page your readers value and a relevant outbound link, without carrying a duplicate-content risk.
You can trim it, and you can wrap it in your own template. Do not change what it says the sky is doing. The content is computed, and the attribution is what lets a reader check that claim.
Daily horoscopes roll over every morning, weekly at the start of the week, monthly on the first day of the calendar month. Pull whenever you like; the API is cached and never makes you wait.
Not in a native app. The program is free because the content stands on a public page or channel that carries the link, and an app has neither. A website or a public Telegram channel is fine; for anything else, write to info@sigastra.com.
Everything here is free. The only condition is a visible link: plus a canonical tag when you publish the full text.
Added the link? Open /api/partners/verify?site=your-domain.com and the content resumes within minutes. A free partner key is issued to your site automatically once the link is measured.